Search for records containing specific text
AI agents call search_records to retrieve information from MCP Template without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data based on a search criterion without creating, modifying, or deleting any records. It has no side effects and falls squarely into the Read category. The severity is low because search operations have minimal blast radius — they cannot corrupt, delete, or alter data. High confidence because the name and description are unambiguous about the read-only nature of the operation.
From the tool's definition Tool name is 'search_records' and description states it will 'Search for records containing specific text' — a pure query operation with no modifications or deletions.
Attacks that exploit this kind of access
Search for records containing specific text. It is categorised as a Read tool in the MCP Template MCP Server, which means it retrieves data without modifying state.
Register the MCP Template MCP server in PolicyLayer and add a rule for search_records: 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 MCP Template. Nothing to install.
search_records 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_records 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_records. 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_records is provided by the MCP Template MCP server (kbhuw/mcp_template). 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 →