Add a new expense to Cosmos DB.
AI agents use add_user_expense to create or update resources in Identity-Aware MCP Server with Azure Cosmos DB — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Identity-Aware MCP Server with Azure Cosmos DB environment.
This tool creates or modifies data reversibly by adding expense entries to Azure Cosmos DB. It is classified as Write rather than Financial because while it records expense data, the actual financial transaction (payment movement) would typically occur separately.
From the tool's definition Tool name 'add_user_expense' and description 'Add a new expense to Cosmos DB' indicate creation of new data records in a database.
Documented attack patterns abuse exactly the kind of access add_user_expense gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Identity-Aware MCP Server with Azure Cosmos DB, and nothing reaches the server without passing your rules. This is the rule we recommend for add_user_expense:
{
"version": "1",
"default": "deny",
"tools": {
"add_user_expense": {
"limits": [
{
"counter": "add_user_expense_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_user_expense stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
All 3 Identity-Aware MCP Server with Azure Cosmos DB tools →
Add a new expense to Cosmos DB. It is categorised as a Write tool in the Identity-Aware MCP Server with Azure Cosmos DB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Identity-Aware MCP Server with Azure Cosmos DB MCP server in PolicyLayer and add a rule for add_user_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 Identity-Aware MCP Server with Azure Cosmos DB. Nothing to install.
add_user_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 add_user_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 add_user_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.
add_user_expense is provided by the Identity-Aware MCP Server with Azure Cosmos DB MCP server (pamelafox/azure-cosmosdb-identity-aware-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Identity-Aware MCP Server with Azure Cosmos DB, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Identity-Aware MCP Server with Azure Cosmos DB tools catalogued and risk-classified — across an index of 43,000+ MCP servers.