openfda_approval_searcher
AI agents call openfda_approval_searcher to retrieve information from CzechMedMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
OpenFDA is a public API providing read-only access to FDA drug approval data. A searcher tool queries and retrieves existing approval information without modifying, deleting, or executing external operations. Although the description is empty (reducing confidence slightly), the tool name strongly indicates a passive search operation typical of Read category tools.
From the tool's definition Tool name 'openfda_approval_searcher' indicates a search/query function against FDA approval data. The '_searcher' suffix and context of searching FDA approvals (a public database) suggest read-only retrieval without side effects.
Attacks that exploit this kind of access
openfda_approval_searcher. It is categorised as a Read tool in the CzechMedMCP MCP Server, which means it retrieves data without modifying state.
Register the CzechMed MCP server in PolicyLayer and add a rule for openfda_approval_searcher: 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 CzechMedMCP. Nothing to install.
openfda_approval_searcher 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 openfda_approval_searcher 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 openfda_approval_searcher. 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.
openfda_approval_searcher is provided by the CzechMed MCP server (petrsovadina/czechmedmcp). 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 →