AI agents call search_device_power_query to retrieve information from OpenFDA FastMCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries FDA medical device clearance data, consistent with the server's stated purpose of enabling agents to 'query and analyze' public datasets. The Read category applies because the tool retrieves data with no side effects. Severity is low because FDA public health data is non-sensitive and querying it poses minimal risk of misuse.
From the tool's definition Tool name 'search_device_power_query' indicates a search/query operation on medical device data. Sibling tools like 'search_drug_labels', 'search_food_events', and 'search_drug_power_query' are all query/search operations that retrieve FDA public health…
Documented attack patterns abuse exactly the kind of access search_device_power_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenFDA FastMCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_device_power_query:
{
"version": "1",
"default": "deny",
"tools": {
"search_device_power_query": {}
}
}search_device_power_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_device_power_query. It is categorised as a Read tool in the OpenFDA FastMCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenFDA FastMCP Server MCP server in PolicyLayer and add a rule for search_device_power_query: 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 OpenFDA FastMCP Server. Nothing to install.
search_device_power_query 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 search_device_power_query 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 search_device_power_query. 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.
search_device_power_query is provided by the OpenFDA FastMCP Server MCP server (suyashekhande/openfda-semantic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenFDA FastMCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 OpenFDA FastMCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.