Export & validate: status|check|claims|drawings_description|
AI agents use export to create or update resources in Patentorney — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Patentorney environment.
This tool exports patent application data (claims, drawings descriptions, etc.) in various formats. While export itself is not inherently destructive, it creates/writes output files or structured data exports. The validation aspect is read-only, but the primary function (export) modifies or creates new data artifacts.
From the tool's definition Tool name 'export' combined with description indicating "Export & validate" with operations like 'status|check|claims|drawings_description|'. Export operations typically write data to files or external formats, creating or modifying output artifacts.
Attacks that exploit this kind of access
Export & validate: status|check|claims|drawings_description|. It is categorised as a Write tool in the Patentorney MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Patentorney MCP server in PolicyLayer and add a rule for export: 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 Patentorney. Nothing to install.
export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export 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 export. 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.
export is provided by the Patentorney MCP server (retospect/patentorney-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 →