Fetch the activity history of a ProofHub task (stage changes, edits, etc.).
AI agents call proofhub_get_task_history to retrieve information from ProofHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information about a ProofHub task (stage changes, edits) without creating, modifying, deleting, executing commands, or moving money. It is purely a query operation that has no side effects on the system or data.
From the tool's definition Tool name includes 'get' and description states 'Fetch the activity history' — both indicate data retrieval with no modification. The history is read-only metadata about past changes to a task.
Attacks that exploit this kind of access
Fetch the activity history of a ProofHub task (stage changes, edits, etc.). It is categorised as a Read tool in the ProofHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ProofHub MCP Server MCP server in PolicyLayer and add a rule for proofhub_get_task_history: 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 MCP Server. Nothing to install.
proofhub_get_task_history 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 proofhub_get_task_history 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 proofhub_get_task_history. 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.
proofhub_get_task_history is provided by the ProofHub MCP Server MCP server (mustafapatharia/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 →