Get compressed briefing + top-k relevant fragments. Call when context window pressure hits.
AI agents call stenographer_compact_guard to retrieve information from Omega Stenographer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns data (compressed briefing and relevant fragments) in response to context window pressure. It performs no writes, deletions, code execution, or financial transactions. The operation is purely informational and non-destructive, making it a straightforward Read category tool with low severity.
From the tool's definition Tool description indicates it 'Get[s] compressed briefing + top-k relevant fragments,' which is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get compressed briefing + top-k relevant fragments. Call when context window pressure hits. It is categorised as a Read tool in the Omega Stenographer MCP Server, which means it retrieves data without modifying state.
Register the Omega Stenographer MCP server in PolicyLayer and add a rule for stenographer_compact_guard: 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 Omega Stenographer. Nothing to install.
stenographer_compact_guard 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 stenographer_compact_guard 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 stenographer_compact_guard. 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.
stenographer_compact_guard is provided by the Omega Stenographer MCP server (vrtxomega/omega-stenographer-mcp). 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 →