AI agents call y2_get_report to retrieve information from Y2 Intel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
reportId | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves a specific report by ID without any side effects or modifications to data. The 'Get' verb and explicit 'reports:read' permission confirm it is a read operation. No execution, writing, deletion, or financial implications are evident. Severity is low because data retrieval presents minimal risk compared to write or destructive operations.
From the tool's definition Tool description explicitly states 'Get one Y2 report by ID' with permission requirement 'reports:read', indicating read-only data retrieval with no modification or execution capabilities.
Attacks that exploit this kind of access
Get one Y2 report by ID. Requires reports:read. It is categorised as a Read tool in the Y2 Intel MCP Server, which means it retrieves data without modifying state.
y2_get_report accepts 1 parameter: reportId. Required: reportId. The full parameter table on this page comes from the server's own tool schema.
Register the Y2 Intel MCP server in PolicyLayer and add a rule for y2_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 Y2 Intel. Nothing to install.
y2_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 y2_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 y2_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.
y2_get_report is provided by the Y2 Intel MCP server (@y2-intel/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
y2_get_report is one line of Y2 Intel's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →