update_tasks_history
Updates 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/update-tasks-history.md
What update_tasks_history does on Wpm Mcp Server
AI agents use update_tasks_history to create or update resources in Wpm Mcp Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wpm Mcp Server environment.
Why update_tasks_history is rated Medium
The tool updates task history records, which is a reversible modification operation (Write category). It is not destructive (no deletion), not financial (no money movement), and not execute (no arbitrary code execution).
From the tool's definition Tool name 'update_tasks_history' and description 'Updates a specific task history record for a task' indicate modification of existing records.
Attacks that exploit this kind of access
The rule that runs update_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 update_tasks_history, this is the rule to start with:
update_tasks_history stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 update_tasks_history call is checked against it from then on.
Questions about update_tasks_history
Updates 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 Write tool in the Wpm Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for update_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.
update_tasks_history is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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