Retrieve a previously generated report by its ID. WHEN TO USE: After calling veroq_generate_report, use this to fetch the completed report content. RETURNS: Full report with title, ticker, tier, creation date, and markdown content (or structured sections). COST: 1 credit. EXAMPLE: {
AI agents call veroq_get_report 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 is a straightforward data retrieval operation with no side effects. The tool fetches and returns existing report content without creating, modifying, or deleting data. While the server provides financial market data, this particular tool only reads/retrieves already-generated reports, making it a Read category tool with low severity.
From the tool's definition Tool retrieves previously generated report content by ID. Description states 'Retrieve a previously generated report' and 'RETURNS: Full report with title, ticker, tier, creation date, and markdown content'. No data modification, deletion, or execution occurs.
Attacks that exploit this kind of access
Retrieve a previously generated report by its ID. WHEN TO USE: After calling veroq_generate_report, use this to fetch the completed report content. RETURNS: Full report with title, ticker, tier, creation date, and markdown content (or structured sections). COST: 1 credit. EXAMPLE: {. 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_get_report: 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_get_report 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_get_report 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_get_report. 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_get_report 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 →