update_app_domain · PlugLayer MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_app_domain does on PlugLayer MCP Server

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

WHY IT NEEDS A POLICY

Why update_app_domain needs a policy

This tool modifies application settings (the domain slug) but does not delete data or irreversibly destroy resources. The change is reversible—the slug can be updated again to a different value. It does not execute arbitrary code, move money, or perform destructive operations. It fits the Write category as it creates or modifies data reversibly.

From the tool's definition 'Update the app's default pluglayer.io route slug' indicates modification of app domain configuration. The description explicitly states this changes the app's routing/domain settings, which is a reversible configuration change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_app_domain Rate-limited

update_app_domain 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_app_domain": {
      "limits": [
        {
          "counter": "update_app_domain_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 PlugLayer MCP Server, so you can run agents against it safely.

FAQ

Questions about update_app_domain

What does the update_app_domain tool do? +

Update the app's default pluglayer.io route slug. Use this when the user chooses the built-in subdomain now and may switch to a custom domain later. It is categorised as a Write tool in the PlugLayer 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_app_domain? +

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

What risk level is update_app_domain? +

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

Can I rate-limit update_app_domain? +

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

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

update_app_domain is provided by the PlugLayer MCP Server MCP server (pluglayer/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.