My_Tool
AI agents call My_Tool to retrieve information from USPTO Final Petition Decisions MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, confidence is reduced. The surrounding tools are all read operations (search, get, fetch), and the server is described as enabling 'access' to USPTO data, implying retrieval rather than modification. No evidence suggests write, execute, destructive, or financial operations. Classified as Read with low-to-medium confidence pending actual tool description.
From the tool's definition The tool lacks a description, making classification difficult. However, based on the server context (USPTO Final Petition Decisions API access) and sibling tool names (all query/search/get operations with no modification or deletion), this tool most likely…
Attacks that exploit this kind of access
My_Tool. It is categorised as a Read tool in the USPTO Final Petition Decisions MCP Server MCP Server, which means it retrieves data without modifying state.
Register the USPTO Final Petition Decisions MCP Server MCP server in PolicyLayer and add a rule for My_Tool: 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 USPTO Final Petition Decisions MCP Server. Nothing to install.
My_Tool 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 My_Tool 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 My_Tool. 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.
My_Tool is provided by the USPTO Final Petition Decisions MCP Server MCP server (john-walkoe/uspto_fpd_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 →