bundle_device_360
FDA medical-device risk dossier: 510(k) clearances + recalls + adverse events (MAUDE), for any device or manufacturer. For medtech, procurement, and compliance agents. Example call: {"name": "insulin pump"} Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/io-github-colinhughes2121-gocreative-agent-api/bundle-device-360.md
What bundle_device_360 does on GoCreative Agent API
AI agents call bundle_device_360 to retrieve information from GoCreative Agent API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes |
Parameters from the server's own tool schema.
Why bundle_device_360 is rated Low
This tool performs lookups and queries of publicly available FDA records. It has no side effects—it does not create, modify, delete, or overwrite data, nor does it execute arbitrary code or move funds. The retrieval of medical-device risk information supports compliance and procurement workflows but constitutes passive data access.
From the tool's definition Tool retrieves FDA medical-device risk data: '510(k) clearances + recalls + adverse events (MAUDE)'. No modification, deletion, or financial transaction occurs; the tool queries and returns historical compliance and safety information.
Attacks that exploit this kind of access
The rule that runs bundle_device_360 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoCreative Agent API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bundle_device_360, this is the rule to start with:
bundle_device_360 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 GoCreative Agent API, apply this rule, and every bundle_device_360 call is checked against it from then on.
Questions about bundle_device_360
FDA medical-device risk dossier: 510(k) clearances + recalls + adverse events (MAUDE), for any device or manufacturer. For medtech, procurement, and compliance agents. Example call: {"name": "insulin pump"} Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the GoCreative Agent API MCP Server, which means it retrieves data without modifying state.
bundle_device_360 accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the GoCreative Agent API MCP server in PolicyLayer and add a rule for bundle_device_360: 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 GoCreative Agent API. Nothing to install.
bundle_device_360 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 bundle_device_360 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 bundle_device_360. 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.
bundle_device_360 is provided by the GoCreative Agent API MCP server (https://api.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoCreative Agent API, and thousands of servers like it.
This server
Across the catalogue