medical.device-udi
FDA GUDID device lookup — identify a marketed medical device by UDI/device identifier, brand, or company. Returns device description, version/model, Rx vs OTC, single-use/kit/combination flags, MRI safety, sterilization, commercial-distribution status, device identifiers (with GS1/HIBCC/ICCBBA is...
This record as markdown: /tools/io-github-2s-io-mcp/medical.device-udi.md
What medical.device-udi does on Mcp
AI agents call medical.device-udi to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why medical.device-udi is rated Low
This is a read-only data lookup tool that retrieves publicly available FDA medical device information. It performs no data modification, deletion, code execution, or financial transactions. The tool simply queries and returns existing device registry data, making it a clear Read category tool with low severity since unauthorized access to this public FDA data poses minimal security risk.
From the tool's definition Tool performs FDA GUDID device lookup that 'identify a marketed medical device by UDI/device identifier, brand, or company' and 'Returns device description, version/model, Rx vs OTC, single-use/kit/combination flags, MRI safety, sterilization,…
Attacks that exploit this kind of access
The rule that runs medical.device-udi safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For medical.device-udi, this is the rule to start with:
medical.device-udi is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every medical.device-udi call is checked against it from then on.
Questions about medical.device-udi
FDA GUDID device lookup — identify a marketed medical device by UDI/device identifier, brand, or company. Returns device description, version/model, Rx vs OTC, single-use/kit/combination flags, MRI safety, sterilization, commercial-distribution status, device identifiers (with GS1/HIBCC/ICCBBA issuing agency), FDA product codes, and GMDN terms. Free, public-domain FDA data. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for medical.device-udi: 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 Mcp. Nothing to install.
medical.device-udi 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 medical.device-udi 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 medical.device-udi. 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.
medical.device-udi is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue