AI agents use create_contract_template to create or update resources in AdButler — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
file | string | Yes | URL or path to the contract template file |
name | string | Yes | Template name |
attributes | string | Yes | JSON-encoded object containing name, email_subject, email_body, and optionally signing_service, basic_inputs, contract_column_inputs, signers |
email_body | string | Yes | Email body text when sending for signature |
email_subject | string | Yes | Email subject line when sending for signature |
Parameters from the server's own tool schema.
The tool creates new contract templates, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money. The 'medium' severity reflects that misuse could create misleading or unauthorized contract templates that could be sent to users via email, potentially causing business or legal complications, but the operation itself is reversible (templates can be deleted or…
From the tool's definition Tool name 'create_contract_template' and description states it 'Create[s] a new contract template' with parameters for name, file, attributes, email_subject, and email_body. This is a creation operation that modifies the contract template database.
Risk signalsAccepts file system path (file)
Attacks that exploit this kind of access
Create a new contract template. Requires name, file, attributes (JSON string), email_subject, and email_body. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_contract_template accepts 5 parameters: file, name, attributes, email_body, email_subject. Required: file, name, attributes, email_body, email_subject. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for create_contract_template: 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 AdButler. Nothing to install.
create_contract_template 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 create_contract_template 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 create_contract_template. 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.
create_contract_template is provided by the AdButler MCP server (adbutler/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 →