Get all blocks data from OnSecurity. Blocks are reusable security finding templates that can be used across different assessments. They contain standardized vulnerability descriptions, risks, and recommendations. Note that you can get how often a block is used, which is a way to get the most comm...
AI agents call get-blocks 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 queries standardized security finding templates and usage statistics. It has no side effects, does not modify data, execute code, delete data, or move money. The blast radius of misuse is minimal - an agent could only read aggregated template and usage data from the OnSecurity system, which does not compromise system integrity or enable harmful actions.
From the tool's definition Tool description states 'Get all blocks data' and 'can get how often a block is used' - purely retrieval operations with no modification, deletion, or execution.
Attacks that exploit this kind of access
Get all blocks data from OnSecurity. Blocks are reusable security finding templates that can be used across different assessments. They contain standardized vulnerability descriptions, risks, and recommendations. Note that you can get how often a block is used, which is a way to get the most common findings ACROSS ALL CLIENTS ONLY as blocks are the basis of findings across pentests and scans. 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-blocks: 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-blocks 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-blocks 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-blocks. 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-blocks 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 →