pressuredesk_get_dossier
Return the latest full dossier for one PressureDesk entity id.
This record as markdown: /tools/dev-autonomyforge-pressuredesk-pressuredesk/pressuredesk-get-dossier.md
What pressuredesk_get_dossier does on PressureDesk
AI agents call pressuredesk_get_dossier to retrieve information from PressureDesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
entityId | string | Yes | PressureDesk entity id to retrieve, such as a scored market or tool-buyer target id. |
Parameters from the server's own tool schema.
Why pressuredesk_get_dossier is rated Low
This tool retrieves or queries data (a dossier) for a given entity ID. The server is explicitly described as 'read-only', and the tool performs no write, execute, destructive, or financial operations. It has minimal blast radius if misused by an AI agent—at worst, it exposes informational data about spend gate policies for APIs.
From the tool's definition Tool description: 'Return the latest full dossier for one PressureDesk entity id.' Server description emphasizes 'Read-only' status. The verb 'Return' indicates data retrieval with no modification or execution.
Attacks that exploit this kind of access
The rule that runs pressuredesk_get_dossier safely
PolicyLayer is an MCP gateway: it sits between your AI agents and PressureDesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pressuredesk_get_dossier, this is the rule to start with:
pressuredesk_get_dossier is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect PressureDesk, apply this rule, and every pressuredesk_get_dossier call is checked against it from then on.
Questions about pressuredesk_get_dossier
Return the latest full dossier for one PressureDesk entity id. It is categorised as a Read tool in the PressureDesk MCP Server, which means it retrieves data without modifying state.
pressuredesk_get_dossier accepts 1 parameter: entityId. Required: entityId. The full parameter table on this page comes from the server's own tool schema.
Register the PressureDesk MCP server in PolicyLayer and add a rule for pressuredesk_get_dossier: 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 PressureDesk. Nothing to install.
pressuredesk_get_dossier 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 pressuredesk_get_dossier 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 pressuredesk_get_dossier. 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.
pressuredesk_get_dossier is provided by the PressureDesk MCP server (https://pressuredesk.autonomyforge.dev/mcp/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on PressureDesk, and thousands of servers like it.
This server
Across the catalogue