get_capability_statement · FHIR MCP Server MCP

WHAT IT DOES

What get_capability_statement does on FHIR MCP Server

AI agents call get_capability_statement to retrieve information from FHIR MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

WHY IT NEEDS A POLICY

Why get_capability_statement needs a policy

This tool queries and retrieves server capability/metadata information, which is a read-only operation with no side effects. It does not create, modify, delete, or execute external operations. The blast radius is minimal as capability statements contain only structural metadata about what endpoints are available, not actual patient or clinical data. Confidence is high given the clear read-only nature.

From the tool's definition Tool name 'get_capability_statement' and description 'Get FHIR server capabilities' indicate retrieval of metadata about server capabilities without modifying or executing operations.

Attacks that exploit this kind of access

Questions about get_capability_statement

What does the get_capability_statement tool do? +

Get FHIR server capabilities. It is categorised as a Read tool in the FHIR MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_capability_statement? +

Register the FHIR MCP Server MCP server in PolicyLayer and add a rule for get_capability_statement: 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 MCP Server. Nothing to install.

What risk level is get_capability_statement? +

get_capability_statement is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_capability_statement? +

Yes. Add a rate_limit block to the get_capability_statement 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.

How do I block get_capability_statement completely? +

Set action: deny in the PolicyLayer policy for get_capability_statement. 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.

What MCP server provides get_capability_statement? +

get_capability_statement is provided by the FHIR MCP Server MCP server (jcafazzo/fhir-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.