Spending history with weekly averages and totals. USE WHEN: reviewing grocery budget, tracking spending trends. Returns spending entries with totals and weekly averages.
AI agents call get_spend_log to retrieve information from TilbudsTrolden without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing spending records to provide summaries and analytics. It has no side effects—it does not create charges, modify accounts, authorize payments, or delete records. The data returned (spending entries, totals, averages) is historical and read-only.
From the tool's definition Tool name 'get_spend_log' and description 'Spending history with weekly averages and totals' indicate retrieval of historical financial data.
Documented attack patterns abuse exactly the kind of access get_spend_log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TilbudsTrolden, and nothing reaches the server without passing your rules. This is the rule we recommend for get_spend_log:
{
"version": "1",
"default": "deny",
"tools": {
"get_spend_log": {}
}
} get_spend_log 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.
Spending history with weekly averages and totals. USE WHEN: reviewing grocery budget, tracking spending trends. Returns spending entries with totals and weekly averages. It is categorised as a Read tool in the TilbudsTrolden MCP Server, which means it retrieves data without modifying state.
Register the TilbudsTrolden MCP server in PolicyLayer and add a rule for get_spend_log: 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 TilbudsTrolden. Nothing to install.
get_spend_log 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_spend_log 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_spend_log. 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_spend_log is provided by the TilbudsTrolden MCP server (olgasafonova/tilbudstrolden-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TilbudsTrolden, 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.
18 TilbudsTrolden tools catalogued and risk-classified — across an index of 43,000+ MCP servers.