Get tasks that are blocking other work.
AI agents call get_blocking_tasks to retrieve information from Quarterback without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about task dependencies and blocking relationships. It queries existing data without modifying, deleting, or executing any operations. The read-only nature and informational purpose make this a Read category tool with low severity, as misuse would only result in unauthorized information disclosure rather than system damage or data loss.
From the tool's definition Tool name 'get_blocking_tasks' and description 'Get tasks that are blocking other work' indicate a retrieval/query operation with no side effects. The verb 'get' is typical of Read category tools.
Attacks that exploit this kind of access
Get tasks that are blocking other work. It is categorised as a Read tool in the Quarterback MCP Server, which means it retrieves data without modifying state.
Register the Quarterback MCP server in PolicyLayer and add a rule for get_blocking_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 Quarterback. Nothing to install.
get_blocking_tasks 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_blocking_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 get_blocking_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.
get_blocking_tasks is provided by the Quarterback MCP server (bobbyrgoldsmith/quarterback). 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 →