manage_forms
AI agents use manage_forms to create or update resources in oxidize-pdf MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your oxidize-pdf MCP Server environment.
Form management typically involves filling, modifying, or updating form fields within PDFs—reversible write operations. Without a description, confidence is moderate. Categorized as Write rather than Execute because form management is usually data modification, not arbitrary code execution. Severity is medium due to potential for modifying document content with organizational or legal implications.
From the tool's definition Tool name 'manage_forms' on a PDF manipulation server suggests form field interaction. Related tools like 'annotate_pdf' and 'manipulate_pdf' indicate write-capable operations. No description provided.
Attacks that exploit this kind of access
manage_forms. It is categorised as a Write tool in the oxidize-pdf MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the oxidize-pdf MCP Server MCP server in PolicyLayer and add a rule for manage_forms: 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 oxidize-pdf MCP Server. Nothing to install.
manage_forms 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 manage_forms 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 manage_forms. 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.
manage_forms is provided by the oxidize-pdf MCP Server MCP server (bzsanti/oxidize-python). 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 →