retrieve_history_tasks_files
Retrieves the metadata for a specific file associated with a task history record.\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-history-tasks-files.md
What retrieve_history_tasks_files does on Wpm Mcp Server
AI agents call retrieve_history_tasks_files 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_history_tasks_files is rated Low
This is a read-only operation that fetches file metadata associated with task history records. There is no data modification, deletion, execution of code, or financial impact. The tool simply queries and returns metadata, which is characteristic of a Read category tool. The low severity reflects the minimal blast radius if misused - an agent could only access existing metadata, not modify systems or data.
From the tool's definition Tool description states 'Retrieves the metadata for a specific file' - retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs retrieve_history_tasks_files 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_history_tasks_files, this is the rule to start with:
retrieve_history_tasks_files 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_history_tasks_files call is checked against it from then on.
Questions about retrieve_history_tasks_files
Retrieves the metadata for a specific file associated with a task history record.\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_history_tasks_files: 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_history_tasks_files 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_history_tasks_files 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_history_tasks_files. 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_history_tasks_files 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