update_tasks_contactrequests · Wpm Mcp Server MCP

WHAT IT DOES

What update_tasks_contactrequests does on Wpm Mcp Server

AI agents use update_tasks_contactrequests 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 IT NEEDS A POLICY

Why update_tasks_contactrequests needs a policy

The tool updates a contact request object, which is a typical write operation that creates or modifies data reversibly. The context of the server (handling applications, payments, refunds, and contact requests) confirms this is data modification. Severity is medium because unintended updates to contact request records could cause operational issues but are generally reversible.

From the tool's definition Tool name begins with 'update_' which indicates modification of existing data. Description states 'Updates a contact request', confirming it modifies data reversibly rather than deleting or executing arbitrary operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_tasks_contactrequests Rate-limited

update_tasks_contactrequests 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_tasks_contactrequests": {
      "limits": [
        {
          "counter": "update_tasks_contactrequests_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Wpm Mcp Server, so you can run agents against it safely.

FAQ

Questions about update_tasks_contactrequests

What does the update_tasks_contactrequests tool do? +

Updates a contact request.\r\n \r\n\r\n<strong>NOTE:</strong> Any field not included in the update request will be set to either an empty string or. 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.

How do I enforce a policy on update_tasks_contactrequests? +

Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for update_tasks_contactrequests: 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 update_tasks_contactrequests? +

update_tasks_contactrequests is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_tasks_contactrequests? +

Yes. Add a rate_limit block to the update_tasks_contactrequests 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 update_tasks_contactrequests completely? +

Set action: deny in the PolicyLayer policy for update_tasks_contactrequests. 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 update_tasks_contactrequests? +

update_tasks_contactrequests 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.