List Sanka Buy requests in the authenticated workspace with optional status filtering.
AI agents call list_buy_requests 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 and queries buy request data from the workspace. The action is read-only; it does not create, modify, delete, or execute any operations. Even with filtering parameters, the outcome is retrieving existing information without side effects. Confidence is high because the description clearly indicates a listing/query operation.
From the tool's definition Tool name uses 'list' verb and description states 'List Sanka Buy requests' with 'optional status filtering' — pure data retrieval with no modification or side effects.
Attacks that exploit this kind of access
List Sanka Buy requests in the authenticated workspace with optional status filtering. 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 list_buy_requests: 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.
list_buy_requests 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 list_buy_requests 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 list_buy_requests. 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.
list_buy_requests 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 →