Закреплённые (сохранённые в профиле) истории юзера.
AI agents call get_pinned_stories to retrieve information from Claudegram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves user stories that are pinned or saved in a profile. This is a data retrieval operation ('get_') with no capability to modify, delete, or execute actions. It has minimal blast radius if misused by an AI agent, as it only reads existing data. Confidence is high because the 'get_' prefix and read-only semantics are unambiguous.
From the tool's definition Tool name 'get_pinned_stories' and description indicating retrieval of 'pinned (saved in profile) stories of a user' — this is a query/retrieval operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Закреплённые (сохранённые в профиле) истории юзера. It is categorised as a Read tool in the Claudegram MCP Server, which means it retrieves data without modifying state.
Register the Claudegram MCP server in PolicyLayer and add a rule for get_pinned_stories: 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.
get_pinned_stories is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_pinned_stories 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 get_pinned_stories. 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.
get_pinned_stories 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 →