AI agents call search_rfcs 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.
This tool retrieves or queries RFC documents based on keywords. It performs a search operation which is inherently read-only with no side effects—it does not create, modify, delete, or execute anything. The classification as Read is appropriate for search and query operations that return information without altering state.
From the tool's definition Tool name is 'search_rfcs' and description states 'Search for RFCs by keyword', indicating query/search functionality with no data modification capability.
Documented attack patterns abuse exactly the kind of access search_rfcs 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 search_rfcs:
{
"version": "1",
"default": "deny",
"tools": {
"search_rfcs": {}
}
}search_rfcs 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.
Search for RFCs by keyword. 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 search_rfcs: 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.
search_rfcs 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 search_rfcs 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 search_rfcs. 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.
search_rfcs 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.