Low Risk

patent_assignee_search

Find patent assignees (companies / organizations) by name fragment. Returns assignee id, organization name, location, and total patents owned. Ranked by patent count.

Part of the Livedatalink server.

patent_assignee_search is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE LIVEDATALINK →

Free to start. No card required.

AI agents call patent_assignee_search to retrieve information from Livedatalink without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though patent_assignee_search only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Livedatalink policy for all 177 tools.

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

ENFORCE ON MY LIVEDATALINK →

View all 177 tools →

These attack patterns abuse exactly the kind of access patent_assignee_search 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 patent_assignee_search only ever does what you allow.

SECURE LIVEDATALINK →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the patent_assignee_search tool do? +

Find patent assignees (companies / organizations) by name fragment. Returns assignee id, organization name, location, and total patents owned. Ranked by patent count.. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on patent_assignee_search? +

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

What risk level is patent_assignee_search? +

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

Can I rate-limit patent_assignee_search? +

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

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

patent_assignee_search is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Livedatalink tool call.

Deterministic rules across all 177 Livedatalink 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.