Create an expense in Sanka. Attachments are optional when the user did not provide or require one. When a receipt or invoice is provided or required, upload the original file first: use upload_expense_attachment for already available base64 payloads, or start_expense_attachment_upload plus append...
AI agents use create_expense to create or update resources in Sanka MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.
This tool creates new expense records in Sanka, which is a reversible write operation that modifies the expense management system. While expenses relate to financial data, the tool itself only creates records rather than moving money or committing financial obligations (which would be Financial category).
From the tool's definition Tool name 'create_expense' combined with description stating 'Create an expense in Sanka' and supporting attachment upload operations indicates data creation. The tool modifies financial records by adding new expense entries to the system.
Attacks that exploit this kind of access
Create an expense in Sanka. Attachments are optional when the user did not provide or require one. When a receipt or invoice is provided or required, upload the original file first: use upload_expense_attachment for already available base64 payloads, or start_expense_attachment_upload plus append_expense_attachment_upload_chunk until done and finish_expense_attachment_upload for client-local PDFs or unreliable large payloads. Attach uploaded file ids with. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for create_expense: 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.
create_expense is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_expense 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 create_expense. 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.
create_expense 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 →