Skip to content

docs(rulebook): Go MCP rules MCP-015/016 + regenerate indexes#11

Merged
jhumel-code merged 1 commit into
mainfrom
feat/go-mcp-rules
Jun 8, 2026
Merged

docs(rulebook): Go MCP rules MCP-015/016 + regenerate indexes#11
jhumel-code merged 1 commit into
mainfrom
feat/go-mcp-rules

Conversation

@jhumel-code

Copy link
Copy Markdown
Collaborator

Summary

Rationale + indexes for the two new Go MCP rules (paired with the trustabl-rules feat/go-mcp-rules branch).

  • Document MCP-015 / MCP-016 in docs/Policy/mcp/tool_definition.md (front-matter + rule-by-rule defense), mirroring the Python/TS description and ambiguous-name rules.
  • Regenerate every POLICY_INDEX.md via gen_index.py: the two new MCP rows plus pre-existing recalibration severity drift in several per-SDK indexes that had not been regenerated.

check_rulebook.py --rules-repo ../trustabl-rules is clean against the paired branch.

Document the two field-based Go MCP rules (MCP-015 no-description, MCP-016
ambiguous-name) in mcp/tool_definition.md, mirroring the Python/TS description
and ambiguous-name rules. The Go SDKs (mark3labs/mcp-go and the official
go-sdk) are added to the policy's coverage and "does not cover" sections —
untyped-params has no analog for statically-typed Go.

gen_index.py regenerates every POLICY_INDEX.md: alongside the two new MCP rows
it also picks up prior recalibration severity drift in several per-SDK indexes
that had not been regenerated after the severity recalibration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant