platform_info
DataEcho platform overview: what it can host, auth state of this connection, docs links. Call this first if unsure.
This record as markdown: /tools/ai-dataecho-mcp/platform-info.md
What platform_info does on Mcp
AI agents call platform_info 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.
Why platform_info is rated Low
This tool retrieves informational data about the platform — capabilities, authentication state, and documentation links. It has no side effects and is purely a read/query operation.
From the tool's definition platform overview: what it can host, auth state of this connection, docs links. Call this first if unsure.
Attacks that exploit this kind of access
The rule that runs platform_info 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 platform_info, this is the rule to start with:
platform_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every platform_info call is checked against it from then on.
Questions about platform_info
DataEcho platform overview: what it can host, auth state of this connection, docs links. Call this first if unsure. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for platform_info: 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.
platform_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the platform_info 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.
Set action: deny in the PolicyLayer policy for platform_info. 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.
platform_info 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.
More on , and thousands of servers like it.
This server
Across the catalogue