Retrieves all task history records for a specific task.\r\n \r\n\r\nThis endpoint can be used for any task type - contact requests, rental owner requests, resident requests or to do\
AI agents call list_tasks_history to retrieve information from Wpm Mcp Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries historical task records. It has no side effects, does not modify data, execute code, delete records, or involve financial transactions. The low severity reflects minimal blast radius if misused—an AI agent could only retrieve existing historical data, which poses limited risk.
From the tool's definition Tool name 'list_tasks_history' and description state it 'Retrieves all task history records for a specific task' with no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
Retrieves all task history records for a specific task.\r\n \r\n\r\nThis endpoint can be used for any task type - contact requests, rental owner requests, resident requests or to do\. It is categorised as a Read tool in the Wpm Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for list_tasks_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 Wpm Mcp Server. Nothing to install.
list_tasks_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 list_tasks_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 list_tasks_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.
list_tasks_history is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-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 →