openfda_device_searcher
AI agents call openfda_device_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.
This tool searches or queries the OpenFDA device database for information retrieval. No description was provided, which slightly reduces confidence, but the naming pattern and server context clearly indicate a data retrieval function with no side effects. Classified as Read with low severity due to the public, informational nature of medical device searches.
From the tool's definition Tool name 'openfda_device_searcher' and context of CzechMedMCP's stated purpose to connect to 'global biomedical sources (PubMed, ClinicalTrials.gov, OpenFDA)' indicates a search/query function.
Attacks that exploit this kind of access
openfda_device_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_device_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_device_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_device_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_device_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_device_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 →