list_tasks_history

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\

SERVERWpm Mcp Server SOURCEwpm-mcp-server-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/wpm-mcp-server/list-tasks-history.md

WHAT IT DOES

What list_tasks_history does on Wpm Mcp Server

AI agents call list_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.

RISK

Why list_tasks_history is rated Low

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

RECOMMENDED RULE

The rule that runs list_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 list_tasks_history, this is the rule to start with:

list_tasks_history Allowed

list_tasks_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_tasks_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Wpm Mcp Server, apply this rule, and every list_tasks_history call is checked against it from then on.

FAQ

Questions about list_tasks_history

What does the list_tasks_history tool do? +

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.

How do I enforce a policy on list_tasks_history? +

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.

What risk level is list_tasks_history? +

list_tasks_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_tasks_history? +

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.

How do I block list_tasks_history completely? +

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.

What MCP server provides list_tasks_history? +

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.

KEEP EXPLORING

More on Wpm Mcp Server, and thousands of servers like it.

This server

All 420 Wpm Mcp Server tools →

Across the catalogue

list_tasks on 0rca Dojo MCP Server →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →