AI agents call get_rfc to retrieve information from RFC MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves publicly available IETF RFC documents. Fetching documents is a read-only operation with no capacity to modify, delete, or execute code. The severity is low because RFC documents are public technical standards with no sensitive data or destructive capability.
From the tool's definition Tool name is 'get_rfc' and description states 'Fetch an RFC document by its number' — this is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_rfc gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RFC MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_rfc:
{
"version": "1",
"default": "deny",
"tools": {
"get_rfc": {}
}
}get_rfc is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch an RFC document by its number. It is categorised as a Read tool in the RFC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RFC MCP Server MCP server in PolicyLayer and add a rule for get_rfc: 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 RFC MCP Server. Nothing to install.
get_rfc 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 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. 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 is provided by the RFC MCP Server MCP server (mjpitz/mcp-rfc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RFC MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 RFC MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.