Restore tasks from archive
AI agents use restore_tasks to create or update resources in Agent Communication MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Communication MCP Server environment.
This tool restores archived tasks, which means it reads from an archive and writes task data back into the active system state. This is a Write operation because it modifies the task system's current state (making archived tasks active again), but it's reversible since the tasks can be re-archived.
From the tool's definition Tool name 'restore_tasks' and description 'Restore tasks from archive' indicate the tool modifies data by recovering previously archived tasks, which is a reversible write operation.
Attacks that exploit this kind of access
Restore tasks from archive. It is categorised as a Write tool in the Agent Communication MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Communication MCP Server MCP server in PolicyLayer and add a rule for restore_tasks: 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 Agent Communication MCP Server. Nothing to install.
restore_tasks 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 restore_tasks 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 restore_tasks. 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.
restore_tasks is provided by the Agent Communication MCP Server MCP server (jerfowler/agent-comm-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 →