This record as markdown: /tools/io-github-portel-dev-ncp/send-photo.md
What send_photo does on Ncp
AI agents use send_photo to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why send_photo is rated Medium
This tool writes/sends data to Telegram via bot API. While photo transmission is technically reversible (messages can be deleted), it commits data to an external platform and has side effects that modify state on a remote service. It does not retrieve data (Read), execute arbitrary code (Execute), irreversibly delete data (Destructive), or handle money (Financial). Write is the appropriate category.
From the tool's definition Tool description states 'Send photo via Telegram bot' - this creates/sends data (a photo message) to an external service (Telegram), which is a reversible action.
Attacks that exploit this kind of access
The rule that runs send_photo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_photo, this is the rule to start with:
send_photo 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every send_photo call is checked against it from then on.
Questions about send_photo
Send photo via Telegram bot. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp 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 Ncp. Nothing to install.
send_photo 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 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.
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.
send_photo is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue