# 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\

Agent View of the PolicyLayer registry record for `retrieve_history_tasks_files`. HTML page: https://policylayer.com/tools/wpm-mcp-server/retrieve-history-tasks-files

## Facts

- Tool: `retrieve_history_tasks_files`
- Server: Wpm Mcp Server (`wpm-mcp-server-mcp`) — https://policylayer.com/tools/wpm-mcp-server.md
- Install: `npx -y wpm-mcp-server-mcp`
- Homepage: git+https://github.com/HGMproperties/wpm-mcp-server.git
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "retrieve_history_tasks_files",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool description states 'Retrieves the metadata for a specific file' - retrieves data without modification or side effects."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Wpm Mcp Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "retrieve_history_tasks_files": {}
  }
}
```

## Other tools on Wpm Mcp Server (419)

- `delete_all_meterreadings_rentals_summary` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-all-meterreadings-rentals-summary.md
- `delete_all_units_rentals_listing` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-all-units-rentals-listing.md
- `delete_associations_appliances` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-associations-appliances.md
- `delete_associations_boardmembers` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-associations-boardmembers.md
- `delete_bills_files` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-bills-files.md
- `delete_checks_bankaccounts_files` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-checks-bankaccounts-files.md
- `delete_history_tasks_files` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-history-tasks-files.md
- `delete_leases_moveouts` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-leases-moveouts.md
- `delete_meterreadings_associations_summary` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-meterreadings-associations-summary.md
- `delete_rentals_appliances` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-rentals-appliances.md
- `delete_rentals_images` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-rentals-images.md
- `delete_units_rentals_images` — Destructive — https://policylayer.com/tools/wpm-mcp-server/delete-units-rentals-images.md
- `inactivate_associations` — Destructive — https://policylayer.com/tools/wpm-mcp-server/inactivate-associations.md
- `inactivate_rentals` — Destructive — https://policylayer.com/tools/wpm-mcp-server/inactivate-rentals.md
- `invoke_api_endpoint` — Execute — https://policylayer.com/tools/wpm-mcp-server/invoke-api-endpoint.md
- `auto_payments_associations_ownershipaccounts` — Financial — https://policylayer.com/tools/wpm-mcp-server/auto-payments-associations-ownershipaccounts.md
- `create_applications_charges` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-applications-charges.md
- `create_applications_payments` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-applications-payments.md
- `create_applications_refunds` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-applications-refunds.md
- `create_auto_pay_applications` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-auto-pay-applications.md
- `create_auto_payment_leases` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-auto-payment-leases.md
- `create_bankaccounts_deposits` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-bankaccounts-deposits.md
- `create_bankaccounts_quickdeposits` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-bankaccounts-quickdeposits.md
- `create_bankaccounts_transfers` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-bankaccounts-transfers.md
- `create_bankaccounts_withdrawals` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-bankaccounts-withdrawals.md
- `create_bills_payments` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-bills-payments.md
- `create_leases_applieddeposits` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-leases-applieddeposits.md
- `create_leases_charges` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-leases-charges.md
- `create_leases_payments` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-leases-payments.md
- `create_leases_recurringpayments` — Financial — https://policylayer.com/tools/wpm-mcp-server/create-leases-recurringpayments.md
- …and 389 more: https://policylayer.com/tools/wpm-mcp-server.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=wpm-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/wpm-mcp-server