提交完整表单
AI agents use submit_form to create or update resources in Intelligent Form Collection MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intelligent Form Collection MCP Server environment.
This tool creates or modifies data in a backend database by committing form records. It is reversible (forms can typically be edited or deleted by other means), so it does not qualify as Destructive. It has no direct financial impact.
From the tool's definition Tool name 'submit_form' and description '提交完整表单' (submit complete form) indicate data creation/modification. Server description mentions 'database storage,' confirming that form submission writes collected data persistently.
Attacks that exploit this kind of access
提交完整表单. It is categorised as a Write tool in the Intelligent Form Collection MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Intelligent Form Collection MCP Server MCP server in PolicyLayer and add a rule for submit_form: 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 Intelligent Form Collection MCP Server. Nothing to install.
submit_form 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 submit_form 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 submit_form. 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.
submit_form is provided by the Intelligent Form Collection MCP Server MCP server (xiaoshi7915/mdtj-mcp-server). 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 →