AI agents call jpo_get_patent_progress to retrieve information from IP-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server context establish this is a query operation against Japanese patent data. The 'get' prefix and naming convention ('_progress') indicate data retrieval. No evidence of write, delete, execution, or financial operations. The empty description lowers confidence slightly, but the consistent pattern of read-only tools across the server and the 'get_' naming convention makes Read the clear category.
From the tool's definition Tool name 'jpo_get_patent_progress' indicates retrieval of patent progress information. Server context shows all sibling tools (jpo_fetch_full_record, jpo_get_divisional_apps, jpo_get_opd_doc_list, jpo_get_patent_citations, jpo_get_patent_documents) are…
Attacks that exploit this kind of access
jpo_get_patent_progress. It is categorised as a Read tool in the IP-MCP MCP Server, which means it retrieves data without modifying state.
Register the IP- MCP server in PolicyLayer and add a rule for jpo_get_patent_progress: 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 IP-MCP. Nothing to install.
jpo_get_patent_progress 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 jpo_get_patent_progress 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 jpo_get_patent_progress. 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.
jpo_get_patent_progress is provided by the IP- MCP server (kitepon-rgb/ip-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →