Load one slip from Sanka by slip id, numeric id, or external reference.
AI agents call get_slip 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.
The tool retrieves a single slip document using an identifier. The verb 'Load' and the read-only nature of the operation (querying by id/reference without modification) classify this as a Read operation. The low severity reflects that retrieval of slip data typically poses minimal risk unless the data itself is highly sensitive, but the operation itself is non-destructive and reversible.
From the tool's definition Tool name 'get_slip' and description 'Load one slip from Sanka by slip id, numeric id, or external reference' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Load one slip from Sanka by slip id, numeric id, or external reference. 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_slip: 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_slip 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_slip 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_slip. 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_slip 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 →