Load one manifest with full review history and lineage context.
AI agents call get_manifest_detail to retrieve information from Academic Figures without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing data (manifest details, review history, and lineage) without creating, modifying, deleting, or executing operations. It is a pure read operation with minimal blast radius if misused by an AI agent, as it only exposes information already stored in the system.
From the tool's definition Tool description states 'Load one manifest' - a retrieval operation with no modification capability. The verb 'load' and context of reading 'review history and lineage context' indicate data querying without side effects.
Attacks that exploit this kind of access
Load one manifest with full review history and lineage context. It is categorised as a Read tool in the Academic Figures MCP Server, which means it retrieves data without modifying state.
Register the Academic Figures MCP server in PolicyLayer and add a rule for get_manifest_detail: 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 Academic Figures. Nothing to install.
get_manifest_detail 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_manifest_detail 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_manifest_detail. 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_manifest_detail is provided by the Academic Figures MCP server (u9401066/academic-figures-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 →