AI agents call get_task to retrieve information from Proofhub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns existing task data based on a ticket number parameter. It has no capability to modify, delete, or execute operations. The default parameter behavior (project and todolist defaulting to context) does not change the read-only nature of the operation. This is a straightforward data retrieval function with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Get the full JSON of a single task' - this is a retrieval operation that queries data without modification or side effects. The verb 'Get' and the operation of fetching a task's JSON representation indicate read-only behavior.
Attacks that exploit this kind of access
Get the full JSON of a single task (accepts the ticket number). project and todolist default to context. It is categorised as a Read tool in the Proofhub MCP Server, which means it retrieves data without modifying state.
Register the Proofhub MCP server in PolicyLayer and add a rule for get_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 Proofhub. Nothing to install.
get_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 get_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 get_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.
get_task is provided by the Proofhub MCP server (yashmody/proofhub-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 →