Search past pressure events. Use this to find relevant past learnings before implementing something. Searches across expected, actual, adaptation, remember, and context_tags.
AI agents call search_pressures to retrieve information from Decision OS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing pressure event data to inform decision-making. It has no side effects, does not execute code, does not modify data, and does not delete or move resources. The blast radius of misuse is minimal—an agent could retrieve unnecessary information but cannot cause harm through this tool alone. This is a straightforward Read operation.
From the tool's definition Tool name is 'search_pressures' and description states 'Search past pressure events' with functionality to search across historical data fields.
Attacks that exploit this kind of access
Search past pressure events. Use this to find relevant past learnings before implementing something. Searches across expected, actual, adaptation, remember, and context_tags. It is categorised as a Read tool in the Decision OS MCP MCP Server, which means it retrieves data without modifying state.
Register the Decision OS MCP server in PolicyLayer and add a rule for search_pressures: 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.
search_pressures 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 search_pressures 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 search_pressures. 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.
search_pressures 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 →