pressable_update_site · Pressable MCP Server MCP

WHAT IT DOES

What pressable_update_site does on Pressable MCP Server

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

WHY IT NEEDS A POLICY

Why pressable_update_site needs a policy

This tool creates or modifies data reversibly by updating site settings. While 'update' operations can have broad effects depending on which settings are modified (potentially affecting site functionality, security, or performance), the action is reversible and does not irreversibly delete data, execute arbitrary code, or move funds. It falls squarely in the Write category.

From the tool's definition Tool name 'pressable_update_site' combined with description 'Update settings for a specific site' clearly indicates modification of existing site configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pressable_update_site Rate-limited

pressable_update_site 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": {
    "pressable_update_site": {
      "limits": [
        {
          "counter": "pressable_update_site_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 Pressable MCP Server, so you can run agents against it safely.

FAQ

Questions about pressable_update_site

What does the pressable_update_site tool do? +

Update settings for a specific site. It is categorised as a Write tool in the Pressable 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 pressable_update_site? +

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

What risk level is pressable_update_site? +

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

Can I rate-limit pressable_update_site? +

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

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

pressable_update_site is provided by the Pressable MCP Server MCP server (pcwprops/pressable-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.