Get per-field citation map for a record (page, bbox, source text for each field).
AI agents call get_record_citations 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.
This tool queries and returns citation information associated with extracted record fields. It performs no side effects, does not modify data, does not execute code, and does not delete or create resources. It is purely a retrieval operation, fitting the 'Read' category.
From the tool's definition The tool 'get_record_citations' retrieves citation metadata (page, bbox, source text) for a record's fields. The verb 'Get' combined with the retrieval-only nature of fetching citations without modification indicates a read operation.
Documented attack patterns abuse exactly the kind of access get_record_citations 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 get_record_citations:
{
"version": "1",
"default": "deny",
"tools": {
"get_record_citations": {}
}
}get_record_citations 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.
Get per-field citation map for a record (page, bbox, source text for each field). 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 get_record_citations: 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.
get_record_citations 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_record_citations 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_record_citations. 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_record_citations 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.