Flag a patient request as urgent for prioritized processing.
AI agents use mark_urgent_request to create or update resources in MCPDischarge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCPDischarge environment.
This tool creates or modifies data (request urgency flags) reversibly within the EHR/discharge coordination system. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial).
From the tool's definition Tool marks/flags a patient request as urgent, modifying request metadata or status in the hospital system. Description explicitly states it modifies processing priority via flagging action.
Attacks that exploit this kind of access
Flag a patient request as urgent for prioritized processing. It is categorised as a Write tool in the MCPDischarge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCPDischarge MCP server in PolicyLayer and add a rule for mark_urgent_request: 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 MCPDischarge. Nothing to install.
mark_urgent_request 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 mark_urgent_request 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 mark_urgent_request. 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.
mark_urgent_request is provided by the MCPDischarge MCP server (prashantsingh1234/mcp_project). 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 →