openfda_shortage_searcher
AI agents call openfda_shortage_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.
The tool performs a search operation on OpenFDA shortage data, which is a read-only retrieval of public health information. No description is provided, lowering confidence slightly, but the naming pattern ('searcher') and position among similar read/query tools (article_searcher, czechmed_browse_diagnosis) strongly indicate this is a data retrieval function with no side effects or data modification capabilities.
From the tool's definition Tool name 'openfda_shortage_searcher' indicates a search operation for FDA shortage data. The 'searcher' suffix and context within a healthcare information server suggest querying/retrieving shortage information without modification.
Attacks that exploit this kind of access
openfda_shortage_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_shortage_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_shortage_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_shortage_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_shortage_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_shortage_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 →