lookup_execution

Read-only lookup for a prior Call by its exact idempotency key. It never submits or retries a Call.

SERVERQverisai SOURCEhttps://mcp.qveris.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/qverisai-qveris-agent-toolkit/lookup-execution.md

WHAT IT DOES

What lookup_execution does on Qverisai

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

RISK

Why lookup_execution is rated Low

Retrieves historical execution data without modifying state or triggering new operations.

From the tool's definition Read-only lookup for a prior Call by its exact idempotency key

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lookup_execution safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Qverisai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lookup_execution, this is the rule to start with:

lookup_execution Allowed

lookup_execution is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lookup_execution": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Qverisai, apply this rule, and every lookup_execution call is checked against it from then on.

FAQ

Questions about lookup_execution

What does the lookup_execution tool do? +

Read-only lookup for a prior Call by its exact idempotency key. It never submits or retries a Call. It is categorised as a Read tool in the Qverisai MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_execution? +

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

What risk level is lookup_execution? +

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

Can I rate-limit lookup_execution? +

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

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

lookup_execution is provided by the Qverisai MCP server (https://mcp.qveris.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Qverisai, and thousands of servers like it.

This server

All 4 Qverisai tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →