AI agents call get_tools_by_ids to retrieve information from Qveris Agent Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to fetch or list tool definitions by their IDs—a pure read operation with no side effects. While it operates within a financial capabilities network, the tool itself only retrieves metadata about available capabilities rather than executing financial operations or modifying state.
From the tool's definition Tool name 'get_tools_by_ids' and function of retrieving/querying tool metadata by identifiers. Description is incomplete/deprecated but the naming pattern and context indicate a read operation that retrieves information about available tools.
Documented attack patterns abuse exactly the kind of access get_tools_by_ids gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qveris Agent Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tools_by_ids:
{
"version": "1",
"default": "deny",
"tools": {
"get_tools_by_ids": {}
}
}get_tools_by_ids is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
[Deprecated: use. It is categorised as a Read tool in the Qveris Agent Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Qveris Agent Toolkit MCP server in PolicyLayer and add a rule for get_tools_by_ids: 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 Qveris Agent Toolkit. Nothing to install.
get_tools_by_ids is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_tools_by_ids 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 get_tools_by_ids. 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.
get_tools_by_ids is provided by the Qveris Agent Toolkit 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.
Deterministic rules across all 8 Qveris Agent Toolkit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Qveris Agent Toolkit tools catalogued and risk-classified — across an index of 42,500+ MCP servers.