telegraph_create_page
AI agents use telegraph_create_page to create or update resources in Telegraph MCP Server (Python) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegraph MCP Server (Python) environment.
This tool creates new Telegraph pages, which is a write operation that modifies state by adding new data to the Telegraph service. While reversible (pages can be deleted), it has moderate blast radius if an AI agent creates numerous pages, spam content, or pages with misleading information.
From the tool's definition Tool name 'telegraph_create_page' indicates creation of new content on Telegraph. Server description explicitly states the tool enables 'create, manage, edit, and export Telegraph pages.' Creation is a reversible write operation.
Attacks that exploit this kind of access
telegraph_create_page. It is categorised as a Write tool in the Telegraph MCP Server (Python) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegraph MCP Server (Python) MCP server in PolicyLayer and add a rule for telegraph_create_page: 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 Telegraph MCP Server (Python). Nothing to install.
telegraph_create_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the telegraph_create_page 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 telegraph_create_page. 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.
telegraph_create_page is provided by the Telegraph MCP Server (Python) MCP server (nehoraihadad/telegraph-mcp-py). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →