AI agents use icost_add_record to create or update resources in Icost App — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Icost App environment.
This tool creates new expense records in the iCost app, modifying the user's financial data reversibly. It falls under Write rather than Financial because it records expenses rather than moving actual money or creating financial obligations. Severity is medium because misuse could lead to incorrect expense logging and financial tracking errors, but records can typically be edited or deleted.
From the tool's definition Tool name 'icost_add_record' indicates it adds/creates a new expense record. Server description mentions 'expense tracking' and 'account operations'. The tool name pattern 'add_*' is characteristic of write operations that create new data.
Documented attack patterns abuse exactly the kind of access icost_add_record gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Icost App, and nothing reaches the server without passing your rules. This is the rule we recommend for icost_add_record:
{
"version": "1",
"default": "deny",
"tools": {
"icost_add_record": {
"limits": [
{
"counter": "icost_add_record_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}icost_add_record 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.
icost_add_record. It is categorised as a Write tool in the Icost App MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Icost App MCP server in PolicyLayer and add a rule for icost_add_record: 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 Icost App. Nothing to install.
icost_add_record 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 icost_add_record 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 icost_add_record. 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.
icost_add_record is provided by the Icost App MCP server (toolife/icost-app-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Icost App, 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.
4 Icost App tools catalogued and risk-classified — across an index of 43,000+ MCP servers.