Load a Sanka Contract workflow state including draft metadata, signers, signature fields, timeline, and editability.
AI agents call get_contract_workflow_state to retrieve information from Sanka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contract workflow metadata and state information without creating, modifying, deleting, or executing any operations. It is a straightforward data read operation with minimal risk if misused by an AI agent, as it only exposes existing contract information.
From the tool's definition Tool name 'get_contract_workflow_state' and description 'Load a Sanka Contract workflow state' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Load a Sanka Contract workflow state including draft metadata, signers, 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.
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 →