Replay a previously saved manifest using the same prompt.
AI agents invoke replay_manifest to trigger actions in Academic Figures. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool re-executes a previously saved manifest, triggering the same multi-step figure generation pipeline (plan, generate, evaluate, etc.) again. It runs an external operation whose effects depend on the saved manifest's arguments, making it Execute category. Misuse could result in unintended regeneration of figures or resource consumption, warranting medium severity.
From the tool's definition Replay a previously saved manifest using the same prompt
Attacks that exploit this kind of access
Replay a previously saved manifest using the same prompt. It is categorised as a Execute tool in the Academic Figures MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Academic Figures MCP server in PolicyLayer and add a rule for replay_manifest: 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.
replay_manifest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the replay_manifest 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 replay_manifest. 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.
replay_manifest 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 →