Архив моих историй (истёкшие, но не удалённые).
AI agents call get_stories_archive 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.
This tool purely retrieves historical story data that has already expired but remains in the archive. It is a read-only operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius is minimal since viewing one's own archived stories poses no security risk to account integrity or external systems.
From the tool's definition Tool description indicates 'Архив моих историй (истёкшие, но не удалённые)' translates to 'Archive of my stories (expired, but not deleted)'. The tool retrieves or queries archived stories without modifying, deleting, or executing external operations.
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_stories_archive: 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_stories_archive 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_stories_archive 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_stories_archive. 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_stories_archive 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 →