update_people_watchlist · Outx MCP: Risk & Policy

WHAT IT DOES

What update_people_watchlist does on Outx

AI agents use update_people_watchlist to create or update resources in Outx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outx environment.

WHY IT NEEDS A POLICY

Why update_people_watchlist needs a policy

This tool modifies watchlist metadata and settings (name, frequency, webhook, pause state) reversibly. These are configuration changes that can be undone by updating again, not destructive deletions. While it affects tracking behavior, there's no code execution, financial impact, or data deletion. The impact is limited to the user's own watchlist settings, giving it medium severity rather than high.

From the tool's definition Tool updates an existing people watchlist by changing name, fetch frequency, Slack webhook configuration, and pause/resume tracking status. The verb 'update' and the description of configuration changes indicate data modification without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_people_watchlist Rate-limited

update_people_watchlist 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_people_watchlist": {
      "limits": [
        {
          "counter": "update_people_watchlist_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 Outx, so you can run agents against it safely.

FAQ

Questions about update_people_watchlist

What does the update_people_watchlist tool do? +

Update a people watchlist. Can change name, fetch frequency, Slack webhook, and pause/resume tracking via. It is categorised as a Write tool in the Outx 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_people_watchlist? +

Register the Outx MCP server in PolicyLayer and add a rule for update_people_watchlist: 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 Outx. Nothing to install.

What risk level is update_people_watchlist? +

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

Can I rate-limit update_people_watchlist? +

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

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

update_people_watchlist is provided by the Outx MCP server (outx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.