get_signature_status
Use this to check signature progress when chasing closing signatures or reporting to the deal team. Returns per-envelope status (sent/signed/declined/voided) for every DocuSign envelope tied to the room.
This record as markdown: /tools/8vdx1-fundos-mcp/get-signature-status.md
What get_signature_status does on Fundos
AI agents call get_signature_status to retrieve information from Fundos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_signature_status is rated Low
This tool queries the status of document signatures without creating, modifying, deleting, or executing any operations. It is purely informational, retrieving signature metadata (sent/signed/declined/voided states) for reporting and monitoring purposes.
From the tool's definition Tool description states it "check[s] signature progress" and "Returns per-envelope status". The action is retrieval-only: examining the state of DocuSign envelopes without modifying them.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_signature_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fundos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_signature_status, this is the rule to start with:
get_signature_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fundos, apply this rule, and every get_signature_status call is checked against it from then on.
Questions about get_signature_status
Use this to check signature progress when chasing closing signatures or reporting to the deal team. Returns per-envelope status (sent/signed/declined/voided) for every DocuSign envelope tied to the room. It is categorised as a Read tool in the Fundos MCP Server, which means it retrieves data without modifying state.
Register the Fundos MCP server in PolicyLayer and add a rule for get_signature_status: 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 Fundos. Nothing to install.
get_signature_status 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 get_signature_status 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 get_signature_status. 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.
get_signature_status is provided by the Fundos MCP server (8vdx1/fundos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fundos, and thousands of servers like it.
This server
Across the catalogue