Get the authenticated user's expense data from Cosmos DB.
AI agents call get_user_expenses to retrieve information from Identity-Aware MCP Server with Azure Cosmos DB without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves expense data for the authenticated user without side effects. It is scoped to the user's own data (authenticated access), involves no data modification, no command execution, and no financial transactions. The read operation has minimal blast radius—at worst, an agent could retrieve a user's own expense history, which does not constitute harm given the authentication boundary.
From the tool's definition Tool name 'get_user_expenses' and description 'Get the authenticated user's expense data from Cosmos DB' indicate a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get_user_expenses 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 get_user_expenses:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_expenses": {}
}
}get_user_expenses is read-only, so it stays allowed — but 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 →
Get the authenticated user's expense data from Cosmos DB. It is categorised as a Read tool in the Identity-Aware MCP Server with Azure Cosmos DB MCP Server, which means it retrieves data without modifying state.
Register the Identity-Aware MCP Server with Azure Cosmos DB MCP server in PolicyLayer and add a rule for get_user_expenses: 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.
get_user_expenses 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_user_expenses 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_user_expenses. 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_user_expenses 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.