Get status + signer responses for a signature envelope. GET /v1/signature/envelopes/{envelope_id}.
AI agents call signature_get_envelope to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a signature envelope (status and signer responses) without creating, modifying, deleting, or executing operations. It is a pure read operation that queries existing data with no side effects, fitting the Read category. Severity is low since information retrieval about signature envelopes poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name includes 'get' and description states 'Get status + signer responses'; uses GET HTTP method to retrieve envelope data without modification.
Documented attack patterns abuse exactly the kind of access signature_get_envelope 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_get_envelope:
{
"version": "1",
"default": "deny",
"tools": {
"signature_get_envelope": {}
}
} signature_get_envelope is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get status + signer responses for a signature envelope. GET /v1/signature/envelopes/{envelope_id}. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for signature_get_envelope: 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_get_envelope is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the signature_get_envelope 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_get_envelope. 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_get_envelope 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.