estimate_query_cost

estimate_query_cost

Server Jiskta jiskta/jiskta-mcp
Category Read
Risk class Low
Parameters 00 required

What estimate_query_cost does on Jiskta

AI agents call estimate_query_cost to retrieve information from Jiskta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why estimate_query_cost needs a policy

The name indicates a read-only operation that queries or estimates costs without side effects. The lack of description lowers confidence, but the semantic meaning of 'estimate' and 'query_cost' strongly suggests retrieval rather than modification, execution, or deletion. Classified as Read with low severity due to the benign nature of cost estimation queries.

From the tool's definition Tool name 'estimate_query_cost' suggests it calculates or retrieves cost information without modifying data. No description provided to confirm behavior.

Questions about estimate_query_cost

What does the estimate_query_cost tool do? +

estimate_query_cost. It is categorised as a Read tool in the Jiskta MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on estimate_query_cost? +

Register the Jiskta MCP server in PolicyLayer and add a rule for estimate_query_cost: 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 Jiskta. Nothing to install.

What risk level is estimate_query_cost? +

estimate_query_cost is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit estimate_query_cost? +

Yes. Add a rate_limit block to the estimate_query_cost 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 estimate_query_cost completely? +

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

estimate_query_cost is provided by the Jiskta MCP server (jiskta/jiskta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.