Create a GoCertta electronic signature envelope (e-signature without ICP-Brasil cert — lower legal weight, faster UX). POST /v1/signature/electronic/envelopes.
AI agents use signature_electronic_create to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool creates a new signature document/envelope, which is a reversible write operation. While signatures have legal implications, the action itself (creating an unsigned envelope for signature collection) is Write-category, not Financial (no money movement) or Destructive (envelopes can be modified or abandoned before signing).
From the tool's definition Tool creates an electronic signature envelope via POST endpoint ('Create a GoCertta electronic signature envelope'). The POST method and 'Create' verb indicate data modification rather than retrieval or deletion.
Documented attack patterns abuse exactly the kind of access signature_electronic_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for signature_electronic_create:
{
"version": "1",
"default": "deny",
"tools": {
"signature_electronic_create": {
"limits": [
{
"counter": "signature_electronic_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}signature_electronic_create stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a GoCertta electronic signature envelope (e-signature without ICP-Brasil cert — lower legal weight, faster UX). POST /v1/signature/electronic/envelopes. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for signature_electronic_create: 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 Mcp Ap2. Nothing to install.
signature_electronic_create 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 signature_electronic_create 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 signature_electronic_create. 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.
signature_electronic_create is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.