Flag a critical decision for tier-A priority.
AI agents use stenographer_mark_milestone to create or update resources in Omega Stenographer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Omega Stenographer environment.
This tool creates or modifies metadata (a priority flag) on existing decision records. It does not delete data (hence not Destructive), execute arbitrary operations (hence not Execute), or move money (hence not Financial). The modification is reversible—the flag can be unmarked.
From the tool's definition Tool description states it 'Flag[s] a critical decision for tier-A priority', indicating modification of metadata or state associated with decision records. The word 'mark' suggests updating a flag or status field.
Attacks that exploit this kind of access
Flag a critical decision for tier-A priority. It is categorised as a Write tool in the Omega Stenographer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Omega Stenographer MCP server in PolicyLayer and add a rule for stenographer_mark_milestone: 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_mark_milestone 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 stenographer_mark_milestone 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_mark_milestone. 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_mark_milestone 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 →