Load one bill from Sanka by bill id, numeric id, or external reference.
AI agents call get_bill 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 a single bill record using identifier parameters. It performs a query/fetch operation without creating, modifying, deleting, or executing anything. The action is read-only retrieval of existing data, which is the lowest risk category. Severity is low because retrieving billing information poses minimal risk even if accessed inappropriately by an AI agent.
From the tool's definition Tool name is 'get_bill' and description states 'Load one bill from Sanka by bill id, numeric id, or external reference' - the verb 'Load' and retrieval-focused operation indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Load one bill from Sanka by bill 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_bill: 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_bill 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_bill 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_bill. 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_bill 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 →