Propose a new observation. Stages it for human approval; does NOT write.
AI agents use propose_observation to create or update resources in Fhir Synthetic — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fhir Synthetic environment.
This tool creates or modifies data (a new observation proposal) but explicitly does not finalize the write—it stages the change for human review and approval. This is a classic Write pattern with compensating controls (human gating, audit logging, ability to reject). The impact is reversible until approved, and even then subject to human oversight.
From the tool's definition Tool name 'propose_observation' and description 'Propose a new observation. Stages it for human approval; does NOT write.' indicate creation of a reversible, staged change (proposal) that requires human approval before commitment.
Attacks that exploit this kind of access
Propose a new observation. Stages it for human approval; does NOT write. It is categorised as a Write tool in the Fhir Synthetic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fhir Synthetic MCP server in PolicyLayer and add a rule for propose_observation: 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.
propose_observation 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 propose_observation 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 propose_observation. 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.
propose_observation 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 →