Check current budget spend — how much is left, percentage used, call details.
AI agents call cost_guard_status to retrieve information from Agent Safety without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves financial budget status information without executing transactions, modifying budgets, or triggering payments. It is a passive read operation that returns budget metrics and spend summaries. While it relates to financial data, it does not move money or commit financial obligations, so it falls under Read rather than Financial category.
From the tool's definition Tool name 'cost_guard_status' and description 'Check current budget spend — how much is left, percentage used, call details' indicates retrieval of budget/spend data with no modification or side effects.
Attacks that exploit this kind of access
Check current budget spend — how much is left, percentage used, call details. It is categorised as a Read tool in the Agent Safety MCP Server, which means it retrieves data without modifying state.
Register the Agent Safety MCP server in PolicyLayer and add a rule for cost_guard_status: 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 Agent Safety. Nothing to install.
cost_guard_status 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 cost_guard_status 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 cost_guard_status. 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.
cost_guard_status is provided by the Agent Safety MCP server (luciferforge/agent-safety-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →