add_sitemap · SergeyKrin9/mcp Servers MCP: Risk & Policy

WHAT IT DOES

What add_sitemap does on SergeyKrin9/mcp Servers

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

WHY IT NEEDS A POLICY

Why add_sitemap needs a policy

The tool creates/registers a new sitemap resource, which is a reversible write operation. It doesn't retrieve data (Read), execute arbitrary code (Execute), permanently delete resources (Destructive), or involve financial transactions (Financial). Severity is medium because incorrect sitemaps could degrade search engine crawling and indexation, but the effect is reversible by deleting/replacing the sitemap.

From the tool's definition Tool registers/adds a new sitemap URL for a host ('Register a new sitemap.xml'). This creates a new resource entry in a webmaster platform (Yandex.Webmaster based on server context), modifying the host's configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_sitemap Rate-limited

add_sitemap 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": {
    "add_sitemap": {
      "limits": [
        {
          "counter": "add_sitemap_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 SergeyKrin9/mcp Servers, so you can run agents against it safely.

FAQ

Questions about add_sitemap

What does the add_sitemap tool do? +

Register a new sitemap.xml (or sitemap-index) URL for the host. Up to 50 per host. It is categorised as a Write tool in the SergeyKrin9/mcp Servers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_sitemap? +

Register the SergeyKrin9/mcp Servers MCP server in PolicyLayer and add a rule for add_sitemap: 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 SergeyKrin9/mcp Servers. Nothing to install.

What risk level is add_sitemap? +

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

Can I rate-limit add_sitemap? +

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

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

add_sitemap is provided by the SergeyKrin9/mcp Servers MCP server (sergeykrin9/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.