add_expense · Demo MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_expense does on Demo MCP Server

AI agents use add_expense to create or update resources in Demo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Demo MCP Server environment.

WHY IT NEEDS A POLICY

Why add_expense needs a policy

The tool name 'add_expense' indicates it creates or adds a new expense entry (write operation on data). While financial in domain, the low severity reflects that it only records an expense rather than moving money or committing financial obligations, and the demo/tutorial context suggests limited real-world impact. Empty description reduces confidence but the name itself is sufficiently clear for categorization.

From the tool's definition Tool name 'add_expense' indicates creation of a new financial record. Description is empty, limiting certainty. Context shows this is a 'Demo MCP Server' with 'basic utility tools' and sibling tool 'list_expenses' suggests financial data management.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_expense Rate-limited

add_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_expense": {
      "limits": [
        {
          "counter": "add_expense_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Demo MCP Server, so you can run agents against it safely.

FAQ

Questions about add_expense

What does the add_expense tool do? +

add_expense. It is categorised as a Write tool in the Demo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_expense? +

Register the Demo MCP Server MCP server in PolicyLayer and add a rule for add_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 Demo MCP Server. Nothing to install.

What risk level is add_expense? +

add_expense is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_expense? +

Yes. Add a rate_limit block to the add_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.

How do I block add_expense completely? +

Set action: deny in the PolicyLayer policy for add_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.

What MCP server provides add_expense? +

add_expense is provided by the Demo MCP Server MCP server (sannketnikam/test-remote-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.