mcp_readme
Fetch setup/config for any MCP server (200 sats/call; free tier 100 calls/mo)
This record as markdown: /tools/com-thetempleofdoom-hyperion-hyperion/mcp-readme.md
What mcp_readme does on Hyperion
AI agents call mcp_readme to retrieve information from Hyperion 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 |
|---|---|---|---|
name | string | Yes | Server name or GitHub URL to look up. |
Parameters from the server's own tool schema.
Why mcp_readme is rated Low
Even though mcp_readme 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
The rule that runs mcp_readme safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hyperion, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_readme, this is the rule to start with:
mcp_readme 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 Hyperion, apply this rule, and every mcp_readme call is checked against it from then on.
Questions about mcp_readme
Fetch setup/config for any MCP server (200 sats/call; free tier 100 calls/mo). It is categorised as a Read tool in the Hyperion MCP Server, which means it retrieves data without modifying state.
mcp_readme accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Hyperion MCP server in PolicyLayer and add a rule for mcp_readme: 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 Hyperion. Nothing to install.
mcp_readme 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 mcp_readme 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 mcp_readme. 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.
mcp_readme is provided by the Hyperion MCP server (https://hyperion.thetempleofdoom.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hyperion, and thousands of servers like it.
This server
Across the catalogue