AI agents call veroq_institutions to retrieve information from Veroq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves public financial data (institutional holdings from SEC 13F filings). It has no side effects, does not execute code, does not modify data, and does not involve financial transactions. The 'WHEN TO USE' clause trails off but the stated function is purely informational lookup. Low severity because institutional ownership data is publicly available and read-only access poses minimal risk.
From the tool's definition Tool retrieves 'institutional ownership data' and 'top holders' from '13F filings' — these are public, historical queries with no modification or execution capability.
Attacks that exploit this kind of access
Get institutional ownership data for a stock — top holders and ownership changes from 13F filings. WHEN TO USE: To see which institutions own a stock and whether they. It is categorised as a Read tool in the Veroq MCP Server, which means it retrieves data without modifying state.
Register the Veroq MCP server in PolicyLayer and add a rule for veroq_institutions: 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 Veroq. Nothing to install.
veroq_institutions 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 veroq_institutions 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 veroq_institutions. 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.
veroq_institutions is provided by the Veroq MCP server (veroq-ai/veroq-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →