Low Risk

evaluate_medical_device

Evaluate Medical Device Profile.

How to control evaluate_medical_device ↓

What evaluate_medical_device does on OpenFDA FastMCP Server

AI agents call evaluate_medical_device 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.

Low Risk

Why evaluate_medical_device needs a policy

This tool retrieves and analyzes data from FDA medical device clearances and related public health datasets. The verb 'evaluate' in context of a profile means to assess or analyze existing information, not to modify or execute external actions.

From the tool's definition Tool name 'evaluate_medical_device' and description 'Evaluate Medical Device Profile' indicate querying/analyzing existing FDA medical device data. The sibling tools all use 'search_' patterns and are explicitly for querying public health datasets.

Documented attack patterns abuse exactly the kind of access evaluate_medical_device gives an agent:

How to control evaluate_medical_device

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 evaluate_medical_device:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "evaluate_medical_device": {}
  }
}

evaluate_medical_device is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OpenFDA FastMCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about evaluate_medical_device

What does the evaluate_medical_device tool do? +

Evaluate Medical Device Profile. It is categorised as a Read tool in the OpenFDA FastMCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on evaluate_medical_device? +

Register the OpenFDA FastMCP Server MCP server in PolicyLayer and add a rule for evaluate_medical_device: 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.

What risk level is evaluate_medical_device? +

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

Can I rate-limit evaluate_medical_device? +

Yes. Add a rate_limit block to the evaluate_medical_device 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 evaluate_medical_device completely? +

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

evaluate_medical_device 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.

Enforce policy on every OpenFDA FastMCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.