call_user_query

A read tool on the AbraFlexi MCP server.

SERVERAbraFlexi SOURCEabraflexi-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/abraflexi/call-user-query.md

WHAT IT DOES

What call_user_query does on AbraFlexi

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

RISK

Why call_user_query is rated Low

Even though call_user_query only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs call_user_query safely

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

call_user_query Allowed

call_user_query 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": {
    "call_user_query": {}
  }
}

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

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

FAQ

Questions about call_user_query

What does the call_user_query tool do? +

call_user_query is a read tool on the AbraFlexi MCP server. It is categorised as a Read tool in the AbraFlexi MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on call_user_query? +

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

What risk level is call_user_query? +

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

Can I rate-limit call_user_query? +

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

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

call_user_query is provided by the AbraFlexi MCP server (abraflexi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AbraFlexi, and thousands of servers like it.

This server

All 64 AbraFlexi tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

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