call
Call a specific remote tool with provided parameters.
This record as markdown: /tools/qverisai-qveris-agent-toolkit/call.md
What call does on Qverisai
AI agents use call to commit financial operations through Qverisai, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why call is rated Critical
This tool executes arbitrary remote tools on a server explicitly designed for financial capabilities. Since the server's primary purpose is routing financial operations (payments, trades, subscriptions, etc.), calling any remote tool could trigger financial transactions. The most severe applicable category is Financial, given the server context.
From the tool's definition 'Call a specific remote tool with provided parameters' on a server described as providing '10,000+ real-world financial capabilities'
Attacks that exploit this kind of access
The rule that runs call 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 call, this is the rule to start with:
Any call to call is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Qverisai, apply this rule, and every call call is checked against it from then on.
Questions about call
Call a specific remote tool with provided parameters. It is categorised as a Financial tool in the Qverisai MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Qverisai MCP server in PolicyLayer and add a rule for call: 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.
call is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the call 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.
Set action: deny in the PolicyLayer policy for call. 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.
call is provided by the Qverisai MCP server (qverisai/qveris-agent-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Qverisai, and thousands of servers like it.
Across the catalogue