AI agents call get_verification_status to retrieve information from Scrumdo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries verification status and QA status information from a card or verification loop without modifying, deleting, or executing operations. It is purely a data retrieval operation with no side effects, fitting the 'Read' category. The low severity reflects minimal blast radius—an agent misusing this tool can only access status information, not alter workflows or data.
From the tool's definition Tool name 'get_verification_status' and description 'The loop's verification snapshot: last verdict, the card's qa_status' indicate retrieval of status information with no mutation of data.
Attacks that exploit this kind of access
The loop's verification snapshot: last verdict, the card's qa_status,. It is categorised as a Read tool in the Scrumdo MCP Server, which means it retrieves data without modifying state.
Register the Scrumdo MCP server in PolicyLayer and add a rule for get_verification_status: 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 Scrumdo. Nothing to install.
get_verification_status 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 get_verification_status 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 get_verification_status. 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.
get_verification_status is provided by the Scrumdo MCP server (scrumdollc/scrumdo-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 →