Medium Risk

fda_resolve_company

Resolve a company name to its canonical company_id and list all known aliases. Returns the canonical slug, match confidence, and alias names. Read-only lookup — does not discover new aliases. Related: fda_suggest_subsidiaries (discover potential subsidiaries not yet aliased), fda_company_full (fu...

Part of the FDA Data MCP server.

fda_resolve_company can modify FDA Data MCP data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE FDA DATA MCP →

Free to start. No card required.

AI agents use fda_resolve_company to create or modify resources in FDA Data MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call fda_resolve_company repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach FDA Data MCP.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fda_resolve_company": {
      "limits": [
        {
          "counter": "fda_resolve_company_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full FDA Data MCP policy for all 48 tools.

Get this rule live on your own FDA Data MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FDA DATA MCP →

View all 48 tools →

These attack patterns abuse exactly the kind of access fda_resolve_company gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so fda_resolve_company only ever does what you allow.

SECURE FDA DATA MCP →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the fda_resolve_company tool do? +

Resolve a company name to its canonical company_id and list all known aliases. Returns the canonical slug, match confidence, and alias names. Read-only lookup — does not discover new aliases. Related: fda_suggest_subsidiaries (discover potential subsidiaries not yet aliased), fda_company_full (full profile using the resolved name).. It is categorised as a Write tool in the FDA Data MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on fda_resolve_company? +

Register the FDA Data MCP server in PolicyLayer and add a rule for fda_resolve_company: 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 FDA Data MCP. Nothing to install.

What risk level is fda_resolve_company? +

fda_resolve_company is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit fda_resolve_company? +

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

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

fda_resolve_company is provided by the FDA Data MCP server (https://www.regdatalab.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every FDA Data MCP tool call.

Deterministic rules across all 48 FDA Data MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.