Verify task completion and quality
AI agents call verify_task to retrieve information from MCP Shrimp Task Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and evaluates task state to confirm completion and assess quality. It performs no writes, deletions, code execution, or financial operations. While it accesses task data, it is non-destructive and has no side effects beyond reading task information.
From the tool's definition Tool name 'verify_task' and description 'Verify task completion and quality' indicate inspection/validation operations without modification or execution capabilities. The verb 'verify' is observational—it checks status rather than modifying or executing tasks.
Attacks that exploit this kind of access
Verify task completion and quality. It is categorised as a Read tool in the MCP Shrimp Task Manager MCP Server, which means it retrieves data without modifying state.
Register the MCP Shrimp Task Manager MCP server in PolicyLayer and add a rule for verify_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 MCP Shrimp Task Manager. Nothing to install.
verify_task 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 verify_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 verify_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.
verify_task is provided by the MCP Shrimp Task Manager MCP server (samihalawa/gist-task-manager-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 →