AI agents call find_records to retrieve information from Sifter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'find_records' and the operational context (searching/querying structured documents) indicate a read operation that retrieves data without side effects. The server's core purpose is to enable queries over document data. No evidence suggests this modifies, deletes, or executes arbitrary code.
From the tool's definition Tool name 'find_records' combined with sibling tools 'list_records', 'get_record_citations', and 'get_sift' indicate query/retrieval operations.
Documented attack patterns abuse exactly the kind of access find_records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sifter, and nothing reaches the server without passing your rules. This is the rule we recommend for find_records:
{
"version": "1",
"default": "deny",
"tools": {
"find_records": {}
}
}find_records 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.
find_records. It is categorised as a Read tool in the Sifter MCP Server, which means it retrieves data without modifying state.
Register the Sifter MCP server in PolicyLayer and add a rule for find_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 Sifter. Nothing to install.
find_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 find_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 find_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.
find_records is provided by the Sifter MCP server (sifter-ai/sifter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Sifter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Sifter tools catalogued and risk-classified — across an index of 42,500+ MCP servers.