get_site

Full details + current file manifest of an owned site.

SERVERMcp SOURCEhttps://dataecho.ai/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_site does on Mcp

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

Parameter	Type	Required	Description
`slug`	string	Yes	Site slug

Parameters from the server's own tool schema.

RISK

Why get_site is rated Low

This tool retrieves metadata and file manifests from an already-owned site without creating, modifying, or deleting any resources. The scope is limited to owned sites (access control is presumed), and the operation is purely informational. Misuse by an AI agent would result in information disclosure rather than resource corruption or destruction.

From the tool's definition Tool name 'get_site' and description 'Full details + current file manifest of an owned site' indicate retrieval of information with no modification or deletion. The verb 'get' and the phrase 'full details' confirm a read-only query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_site 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 get_site, this is the rule to start with:

get_site Allowed

get_site 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": {
    "get_site": {}
  }
}

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

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

FAQ

Questions about get_site

What does the get_site tool do? +

Full details + current file manifest of an owned site. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does get_site accept? +

get_site accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_site? +

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

What risk level is get_site? +

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

Can I rate-limit get_site? +

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

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

get_site 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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