AI agents call list_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.
Despite the empty description, the tool name 'list_records' and contextual evidence from sibling tools strongly indicate this is a data retrieval operation with no side effects. Listing records is a standard read-only query operation. Severity is low because listing data poses minimal risk if misused by an agent.
From the tool's definition Tool name 'list_records' combined with sibling tools like 'find_records', 'get_record_citations', and 'get_sift' that are clearly data retrieval operations.
Documented attack patterns abuse exactly the kind of access list_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 list_records:
{
"version": "1",
"default": "deny",
"tools": {
"list_records": {}
}
}list_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.
list_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 list_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.
list_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 list_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 list_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.
list_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.