Generate a Japanese partner payment request notice from calculated incentive rows. This does not create or update Sanka records.
AI agents call generate_incentive_payment_notice 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 generates a payment notice document from existing incentive data but explicitly states it does not create or update any records. This is effectively a read/report operation with no side effects, making it a Read category tool with low severity.
From the tool's definition 'This does not create or update Sanka records' — the tool only generates a document/notice without persisting any data
Attacks that exploit this kind of access
Generate a Japanese partner payment request notice from calculated incentive rows. This does not create or update Sanka records. 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 generate_incentive_payment_notice: 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.
generate_incentive_payment_notice 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 generate_incentive_payment_notice 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 generate_incentive_payment_notice. 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.
generate_incentive_payment_notice 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 →