telegraph_edit_account_info

WHAT IT DOES

What telegraph_edit_account_info does on Telegraph MCP Server (Python)

AI agents use telegraph_edit_account_info 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.

WHY IT NEEDS A POLICY

Why telegraph_edit_account_info needs a policy

This tool modifies account metadata reversibly (account info can be changed again), making it a Write operation rather than Read (which would only retrieve info) or Destructive (which would delete it irreversibly). The medium severity reflects that account info changes could affect access control or reputation, but are not irreversible or financial.

From the tool's definition Tool name is 'telegraph_edit_account_info' with an empty description. The prefix 'edit' indicates modification of existing data. The suffix 'account_info' indicates it modifies account-level metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

telegraph_edit_account_info Rate-limited

telegraph_edit_account_info stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "telegraph_edit_account_info": {
      "limits": [
        {
          "counter": "telegraph_edit_account_info_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Telegraph MCP Server (Python), so you can run agents against it safely.

FAQ

Questions about telegraph_edit_account_info

What does the telegraph_edit_account_info tool do? +

telegraph_edit_account_info. 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.

How do I enforce a policy on telegraph_edit_account_info? +

Register the Telegraph MCP Server (Python) MCP server in PolicyLayer and add a rule for telegraph_edit_account_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 Telegraph MCP Server (Python). Nothing to install.

What risk level is telegraph_edit_account_info? +

telegraph_edit_account_info is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit telegraph_edit_account_info? +

Yes. Add a rate_limit block to the telegraph_edit_account_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.

How do I block telegraph_edit_account_info completely? +

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

What MCP server provides telegraph_edit_account_info? +

telegraph_edit_account_info 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.