Get the reference list of a given paper (forward citation tracking).
AI agents call search_references to retrieve information from Q1 Crafter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves citation metadata from an existing paper. It performs a lookup/query operation without creating, modifying, deleting, executing code, or committing financial obligations. The only potential concern is that repeated calls could be rate-limited by external APIs, but the tool itself is fundamentally a Read operation.
From the tool's definition Tool description states "Get the reference list of a given paper" — a retrieval operation with no modification or side effects. The phrase "forward citation tracking" confirms it queries and returns existing citation data.
Attacks that exploit this kind of access
Get the reference list of a given paper (forward citation tracking). It is categorised as a Read tool in the Q1 Crafter MCP MCP Server, which means it retrieves data without modifying state.
Register the Q1 Crafter MCP server in PolicyLayer and add a rule for search_references: 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 Q1 Crafter MCP. Nothing to install.
search_references 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_references 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_references. 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_references is provided by the Q1 Crafter MCP server (muslus/q1-crafter-mcp). 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 →