AI agents call get_related_sections to retrieve information from Rfcxml without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about RFC document sections. It performs a lookup or search operation without creating, modifying, deleting, or executing any code. The action is purely informational and reversible, fitting squarely within the Read category. The low severity reflects that misuse would only expose existing RFC documentation without operational impact.
From the tool's definition Tool name 'get_related_sections' and description 'Get sections related to the specified section' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get sections related to the specified section. It is categorised as a Read tool in the Rfcxml MCP Server, which means it retrieves data without modifying state.
Register the Rfcxml MCP server in PolicyLayer and add a rule for get_related_sections: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Rfcxml. Nothing to install.
get_related_sections is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_related_sections rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_related_sections. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_related_sections is provided by the Rfcxml MCP server (shuji-bonji/rfcxml-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →