get_contract_workflow_state
Load a Sanka Contract workflow state including draft metadata, signers, non-signing CC recipients, signature fields, timeline, and editability.
This record as markdown: /tools/sankahq-sanka-mcp/get-contract-workflow-state.md
What get_contract_workflow_state does on Sanka MCP Server
AI agents call get_contract_workflow_state to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_contract_workflow_state is rated Low
This tool retrieves and queries contract workflow information without creating, modifying, or deleting data. It is a read-only operation that returns existing contract state metadata. The blast radius is minimal as it only exposes information access without side effects.
From the tool's definition Tool name contains 'get_' prefix and description uses 'Load' indicating data retrieval. The description specifies reading workflow state, metadata, signers, and other document information with no mention of modifications, deletions, or state changes.
Attacks that exploit this kind of access
The rule that runs get_contract_workflow_state safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_contract_workflow_state, this is the rule to start with:
get_contract_workflow_state 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 Sanka MCP Server, apply this rule, and every get_contract_workflow_state call is checked against it from then on.
Questions about get_contract_workflow_state
Load a Sanka Contract workflow state including draft metadata, signers, non-signing CC recipients, signature fields, timeline, and editability. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for get_contract_workflow_state: 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 Sanka MCP Server. Nothing to install.
get_contract_workflow_state 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_contract_workflow_state 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_contract_workflow_state. 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_contract_workflow_state is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue