sitemap_stats

Sitemap coverage: how many pages exist, are indexable, and are actually indexed. Read-only.

SERVER0nmcp SOURCE0nmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-0nork-0nmcp/sitemap-stats.md

WHAT IT DOES

What sitemap_stats does on 0nmcp

AI agents call sitemap_stats to retrieve information from 0nmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why sitemap_stats is rated Low

Even though sitemap_stats only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sitemap_stats safely

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

sitemap_stats Allowed

sitemap_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sitemap_stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sitemap_stats

What does the sitemap_stats tool do? +

Sitemap coverage: how many pages exist, are indexable, and are actually indexed. Read-only. It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sitemap_stats? +

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

What risk level is sitemap_stats? +

sitemap_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sitemap_stats? +

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

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

sitemap_stats is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 0n, and thousands of servers like it.

This server

All 218 0n tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →