Show context budget: tokens consumed, tokens saved, percentage used, warnings.
AI agents call lctx_budget to retrieve information from Logica Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing budget statistics and metrics. The verb 'Show' and the list of read-only information (tokens consumed, tokens saved, percentage used, warnings) confirm it performs a passive query with no side effects, state modifications, or external operations.
From the tool's definition Tool name 'lctx_budget' and description 'Show context budget: tokens consumed, tokens saved, percentage used, warnings' indicate a read-only query operation that retrieves and displays metrics about resource usage without modifying state.
Attacks that exploit this kind of access
Show context budget: tokens consumed, tokens saved, percentage used, warnings. It is categorised as a Read tool in the Logica Context MCP Server, which means it retrieves data without modifying state.
Register the Logica Context MCP server in PolicyLayer and add a rule for lctx_budget: 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 Logica Context. Nothing to install.
lctx_budget 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 lctx_budget 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 lctx_budget. 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.
lctx_budget is provided by the Logica Context MCP server (rovemark/logica-context). 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 →