Get all rounds data from OnSecurity from client in a high level summary. When replying, only include the summary, not the raw data and be sure to present the data in a way that is easy to understand for the client. Rounds can be pentest rounds, scan rounds, or radar rounds.
AI agents call get-rounds to retrieve information from OnSecurity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and summarizes security assessment data (pentest, scan, and radar rounds) from the OnSecurity platform. It performs no creation, modification, deletion, code execution, or financial operations. The blast radius of misuse is limited to information disclosure of existing security assessment summaries, which constitutes low severity for a read-only data access tool.
From the tool's definition Tool description states 'Get all rounds data' and 'only include the summary, not the raw data' — explicitly a retrieval operation with no modification capability. The verb 'Get' and context of summarizing security findings data confirm read-only access.
Attacks that exploit this kind of access
Get all rounds data from OnSecurity from client in a high level summary. When replying, only include the summary, not the raw data and be sure to present the data in a way that is easy to understand for the client. Rounds can be pentest rounds, scan rounds, or radar rounds. It is categorised as a Read tool in the OnSecurity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OnSecurity MCP Server MCP server in PolicyLayer and add a rule for get-rounds: 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 OnSecurity MCP Server. Nothing to install.
get-rounds 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-rounds 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-rounds. 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-rounds is provided by the OnSecurity MCP Server MCP server (onsecurity/onsecurity-mcp-server). 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 →