Отправить геолокацию.
AI agents use send_location to create or update resources in Claudegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claudegram environment.
The tool sends location data to a Telegram chat, which is a creation/transmission action (Write category). Severity is medium because: (1) it can be used to share sensitive location information with unintended recipients if the agent targets the wrong chat, and (2) while reversible via message deletion in Telegram, the data exposure occurs immediately upon send.
From the tool's definition Tool name 'send_location' and description 'Отправить геолокацию' (Send geolocation) indicate the tool creates and transmits a new message/location data to a Telegram chat. This is a reversible write operation that modifies chat state by adding a new message.
Attacks that exploit this kind of access
Отправить геолокацию. It is categorised as a Write tool in the Claudegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claudegram MCP server in PolicyLayer and add a rule for send_location: 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 Claudegram. Nothing to install.
send_location 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_location 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_location. 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_location is provided by the Claudegram MCP server (sanjar-x/claudegram). 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 →