AI agents use sync_all_resumes to create or update resources in Narrarium — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Narrarium environment.
The tool performs bulk updates to multiple resumes (chapter-level and book-level summaries) in a single operation. This is reversible (resumes can be regenerated or reverted) and creates/modifies data rather than executing arbitrary code or destructively deleting data.
From the tool's definition Tool description states it will 'Refresh every chapter resume and the total book resume in one pass' — this modifies existing data (chapter and book resumes) by updating them, which is a Write operation rather than merely reading.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Refresh every chapter resume and the total book resume in one pass. It is categorised as a Write tool in the Narrarium MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Narrarium MCP server in PolicyLayer and add a rule for sync_all_resumes: 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 Narrarium. Nothing to install.
sync_all_resumes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sync_all_resumes 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 sync_all_resumes. 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.
sync_all_resumes is provided by the Narrarium MCP server (narrarium-mcp-server). 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 →