Low Risk

query_blocklist

Check whether a value is currently on the Konduto blocklist.

How to control query_blocklist ↓

What query_blocklist does on Mcp Ap2

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

Low Risk

Why query_blocklist needs a policy

This tool retrieves blocklist status information for audit/fraud-prevention purposes. It performs a lookup query without side effects, making it a Read operation. Severity is low because misuse (e.g., querying the blocklist for reconnaissance) poses minimal risk compared to financial or destructive operations. The AP2 context (payment protocol) does not change the fundamental nature of this query-only tool.

From the tool's definition Tool name 'query_blocklist' and description 'Check whether a value is currently on the Konduto blocklist' indicate a read-only query operation with no data modification, creation, deletion, or financial transaction effects.

Documented attack patterns abuse exactly the kind of access query_blocklist gives an agent:

How to control query_blocklist

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for query_blocklist:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_blocklist": {}
  }
}

query_blocklist is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about query_blocklist

What does the query_blocklist tool do? +

Check whether a value is currently on the Konduto blocklist. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_blocklist? +

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

What risk level is query_blocklist? +

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

Can I rate-limit query_blocklist? +

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

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

query_blocklist is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, 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.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.