Quick-capture a pressure event with minimal friction. Use this when you want to capture a surprise fast without filling all fields. Only requires expected and actual — adaptation and remember are optional (remember is auto-generated from expected vs actual if omitted). Prefer this over log_pressu...
AI agents use quick_pressure to create or update resources in Decision OS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Decision OS MCP environment.
This tool creates a new record (a 'pressure event') in the decision tracking system. It is a lightweight write operation that captures unexpected outcomes. There are no destructive, financial, or execution-level side effects described. The blast radius of misuse is low — it could create spurious or misleading log entries, but data is not deleted or irrecoverably altered.
From the tool's definition 'Quick-capture a pressure event with minimal friction' and 'Capturing too much is better than missing surprises' — the tool logs/records a new pressure event entry into the system
Attacks that exploit this kind of access
Quick-capture a pressure event with minimal friction. Use this when you want to capture a surprise fast without filling all fields. Only requires expected and actual — adaptation and remember are optional (remember is auto-generated from expected vs actual if omitted). Prefer this over log_pressure when in the middle of debugging or rapid iteration. Capturing too much is better than missing surprises. It is categorised as a Write tool in the Decision OS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Decision OS MCP server in PolicyLayer and add a rule for quick_pressure: 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 Decision OS MCP. Nothing to install.
quick_pressure 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 quick_pressure 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 quick_pressure. 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.
quick_pressure is provided by the Decision OS MCP server (marianstefi20/decision-os-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 →