query_facts

THE RISK

Low Risk

Why query_facts needs a policy

This tool queries existing facts from a knowledge graph/blackboard with filters. No side effects are described; it performs data retrieval only. The verb 'query' and absence of any language indicating creation, modification, deletion, or execution places this firmly in the Read category.

From the tool's definition Tool name 'query_facts' and description 'Query facts from the blackboard with optional filters' indicate a read-only operation that retrieves data without modification or execution.

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

POLICY

How to control query_facts

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

policy.json

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

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

Create a free account and register Iconsult MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Iconsult MCP tools

Execute emit_event EVENT (emit) — Emit a consultation event for reactive processing. Write build_project_kg BUILD PROJECT KG — Build the per-project canonical layer for Write start_project START PROJECT — Create or refresh a per-project cache row. Write assert_fact BLACKBOARD (assert) — Assert a typed, versioned fact on the blackboard. Write log_pattern_assessment LOG ASSESSMENT — Record a pattern assessment for a consultation session. Write rate_consultation QUALITY (rate) — Rate a consultation Write generate_implementation_plan IMPLEMENTATION PLAN — Generate a phased, classified implementation plan Write plan_consultation PLAN — Generate an adaptive consultation plan after match_concepts.

All 29 Iconsult MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about query_facts

What does the query_facts tool do? +

BLACKBOARD (query) — Query facts from the blackboard with optional filters. It is categorised as a Read tool in the Iconsult MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_facts? +

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

What risk level is query_facts? +

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

Can I rate-limit query_facts? +

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

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

query_facts is provided by the Iconsult MCP server (marcus-waldman/iconsult_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Iconsult MCP tool call.

Start from Iconsult MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →