Get RFC section hierarchy and metadata. Metadata is enriched from the IETF Datatracker API (category, stream, publication date, abstract). Pass includeAuthors=true to also resolve author names (incurs extra API calls).
AI agents call get_rfc_structure 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 queries structured information about RFC documents without creating, modifying, deleting, or executing any operations. The optional author name resolution is still a read operation that incurs additional API calls but performs no side effects. No irreversible actions, code execution, or financial implications are present.
From the tool's definition Tool description explicitly states it 'Get[s] RFC section hierarchy and metadata' and retrieves data 'from the IETF Datatracker API' with optional author resolution. Uses query verbs (get) with no modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
Get RFC section hierarchy and metadata. Metadata is enriched from the IETF Datatracker API (category, stream, publication date, abstract). Pass includeAuthors=true to also resolve author names (incurs extra API calls). 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_rfc_structure: 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_rfc_structure 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_rfc_structure 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_rfc_structure. 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_rfc_structure 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 →