Get all tasks that are not blocked and ready to work on
AI agents call oscribble_get_unblocked_tasks to retrieve information from Oscribble MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves task data filtered by blocker status. It performs no mutations, deletions, or state changes—purely a read operation to list tasks matching criteria. The low severity reflects minimal risk even if misused, as retrieving task information cannot damage data or cause adverse effects.
From the tool's definition Tool name 'oscribble_get_unblocked_tasks' and description 'Get all tasks that are not blocked and ready to work on' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all tasks that are not blocked and ready to work on. It is categorised as a Read tool in the Oscribble MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Oscribble MCP Server MCP server in PolicyLayer and add a rule for oscribble_get_unblocked_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 Oscribble MCP Server. Nothing to install.
oscribble_get_unblocked_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 oscribble_get_unblocked_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 oscribble_get_unblocked_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.
oscribble_get_unblocked_tasks is provided by the Oscribble MCP Server MCP server (oscargavin/oscribble-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 →