retrieve_tasks_history
Retrieves a specific task history record for a 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\
This record as markdown: /tools/wpm-mcp-server/retrieve-tasks-history.md
What retrieve_tasks_history does on Wpm Mcp Server
AI agents call retrieve_tasks_history to retrieve information from Wpm Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why retrieve_tasks_history is rated Low
This tool performs a read-only operation that queries and returns task history data without modifying, deleting, or executing any actions. It is a straightforward data retrieval endpoint. The severity is low because retrieving task history records poses minimal security risk even if accessed by an unauthorized agent.
From the tool's definition Tool name 'retrieve_tasks_history' and description states it 'Retrieves a specific task history record' with no mutation, deletion, or side-effects mentioned.
Attacks that exploit this kind of access
The rule that runs retrieve_tasks_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wpm Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For retrieve_tasks_history, this is the rule to start with:
retrieve_tasks_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Wpm Mcp Server, apply this rule, and every retrieve_tasks_history call is checked against it from then on.
Questions about retrieve_tasks_history
Retrieves a specific task history record for a 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 retrieve_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.
retrieve_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 retrieve_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 retrieve_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.
retrieve_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.
More on Wpm Mcp Server, and thousands of servers like it.
This server
Across the catalogue