Medium Risk

send_photo

Send a photo to the configured Telegram user. Accepts a URL or local file path.

Part of the Telegram Notify server.

send_photo can modify Telegram Notify data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE TELEGRAM NOTIFY →

Free to start. No card required.

AI agents use send_photo to create or modify resources in Telegram Notify. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call send_photo repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Telegram Notify.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_photo": {
      "limits": [
        {
          "counter": "send_photo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Telegram Notify policy for all 3 tools.

Get this rule live on your own Telegram Notify server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TELEGRAM NOTIFY →

These attack patterns abuse exactly the kind of access send_photo gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so send_photo only ever does what you allow.

SECURE TELEGRAM NOTIFY →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the send_photo tool do? +

Send a photo to the configured Telegram user. Accepts a URL or local file path.. It is categorised as a Write tool in the Telegram Notify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_photo? +

Register the Telegram Notify MCP server in PolicyLayer and add a rule for send_photo: 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 Telegram Notify. Nothing to install.

What risk level is send_photo? +

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

Can I rate-limit send_photo? +

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

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

send_photo is provided by the Telegram Notify MCP server (@parthj/telegram-notify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Telegram Notify tool call.

Deterministic rules across all 3 Telegram Notify tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.