AI agents use complete_a_task to create or update resources in Interview — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Interview environment.
This tool modifies task state reversibly by changing a task's status to 'complete/terminated'. This is a Write operation because it alters existing data in a way that can be undone (the task can theoretically be reopened or its status changed back). It is not Destructive because the task record persists and the action is reversible.
From the tool's definition Tool description states it can 'Complete, terminate o finalizar una tarea / task' with parameters for task name and list name. The action modifies the status of a task (marking it complete) but does not delete or permanently remove data.
Attacks that exploit this kind of access
Complete, terminate o finalizar una tarea / task con nombre 'name' en la lista llamada 'listname'. It is categorised as a Write tool in the Interview MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Interview MCP server in PolicyLayer and add a rule for complete_a_task: 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 Interview. Nothing to install.
complete_a_task 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 complete_a_task 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 complete_a_task. 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.
complete_a_task is provided by the Interview MCP server (matilarrazabal/mcp-server-interview). 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 →