List writes awaiting human approval.
AI agents call list_pending_writes to retrieve information from Fhir Synthetic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves information about pending write requests. It does not create, modify, delete, or execute any data changes. The tool simply queries the state of the approval workflow.
From the tool's definition Tool name 'list_pending_writes' and description 'List writes awaiting human approval' indicate a query/retrieval operation with no side effects. Returns status of pending operations without modifying data.
Attacks that exploit this kind of access
List writes awaiting human approval. It is categorised as a Read tool in the Fhir Synthetic MCP Server, which means it retrieves data without modifying state.
Register the Fhir Synthetic MCP server in PolicyLayer and add a rule for list_pending_writes: 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 Fhir Synthetic. Nothing to install.
list_pending_writes 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 list_pending_writes 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 list_pending_writes. 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.
list_pending_writes is provided by the Fhir Synthetic MCP server (krishnakakani-github/fhir-synthetic-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 →