patent_ownership_audit

Audits patent ownership for employees or contractors, identifying gaps where inventors may not have properly assigned patent rights to the company. Designed for CHROs to ensure IP compliance and mitigate legal risks. Inputs: employee/contractor names or IDs, optional date range. Outputs: list of ...

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io
Low RISK CLASS
Category Read
Parameters 41 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/patent-ownership-audit.md

What patent_ownership_audit does on Mcp Knowledge

AI agents call patent_ownership_audit to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
async boolean If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
dateRange object Optional date range for patent filings
employeeIds array List of employee or contractor IDs (optional if names provided)
employeeNames array Yes List of employee or contractor full names to audit

Parameters from the server's own tool schema.

Why patent_ownership_audit is rated Low

This tool retrieves and analyzes existing patent data from public records to flag compliance gaps. While it has a compliance/audit purpose, the core functionality is querying and reviewing patent records without modifying them. No data is created, modified, or deleted.

From the tool's definition Tool audits and identifies patent ownership status by querying USPTO PatFT and EPO Espacenet public records, retrieving and analyzing data about patents, ownership status, and assignment details.

Questions about patent_ownership_audit

What does the patent_ownership_audit tool do? +

Audits patent ownership for employees or contractors, identifying gaps where inventors may not have properly assigned patent rights to the company. Designed for CHROs to ensure IP compliance and mitigate legal risks. Inputs: employee/contractor names or IDs, optional date range. Outputs: list of patents, ownership status, flagged gaps, and assignment details. Sources: USPTO PatFT and EPO Espacenet public records. Keywords: patent audit, IP compliance, employee inventions, contractor agreements, CHRO. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

What parameters does patent_ownership_audit accept? +

patent_ownership_audit accepts 4 parameters: async, dateRange, employeeIds, employeeNames. Required: employeeNames. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on patent_ownership_audit? +

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

What risk level is patent_ownership_audit? +

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

Can I rate-limit patent_ownership_audit? +

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

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

patent_ownership_audit is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mcp Knowledge, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Knowledge's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.