update_site_metadata

Patch site settings without redeploying: viewer title/description, SPA mode, TTL, password (string sets, null removes).

SERVERMcp SOURCEhttps://dataecho.ai/mcp

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-dataecho-mcp/update-site-metadata.md

WHAT IT DOES

What update_site_metadata does on Mcp

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

Parameter	Type	Required	Description
`slug`	string	Yes	Site slug
`title`	string	—	Viewer title
`spaMode`	boolean	—	SPA fallback routing
`password`	string	—	Password-gate the site; pass an empty string to REMOVE the password
`ttlSeconds`	number	—	Expiry in seconds (null-like 0 not allowed; omit to keep)
`description`	string	—	Viewer description

Parameters from the server's own tool schema.

RISK

Why update_site_metadata is rated Medium

This tool creates or modifies site configuration metadata (title, description, SPA mode, TTL, password) without executing arbitrary code or permanently deleting data. These are reversible updates to site properties. While password changes could have security implications, the capability itself is a Write operation.

From the tool's definition Tool description states "Patch site settings" which modifies configuration data (viewer title/description, SPA mode, TTL, password).

Risk signalsHandles credentials or secrets (password)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_site_metadata safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_site_metadata, this is the rule to start with:

update_site_metadata Rate-limited

update_site_metadata 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_site_metadata": {
      "limits": [
        {
          "counter": "update_site_metadata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every update_site_metadata call is checked against it from then on.

FAQ

Questions about update_site_metadata

What does the update_site_metadata tool do? +

Patch site settings without redeploying: viewer title/description, SPA mode, TTL, password (string sets, null removes). It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_site_metadata accept? +

update_site_metadata accepts 6 parameters: slug, title, spaMode, password, ttlSeconds, description. Required: slug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_site_metadata? +

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

What risk level is update_site_metadata? +

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

Can I rate-limit update_site_metadata? +

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

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

update_site_metadata is provided by the MCP server (https://dataecho.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 26 tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →