AI agents call get_block_info to retrieve information from Pl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about block packages from a registry without creating, modifying, deleting, or executing any operations. It is informational in nature and has no side effects beyond data retrieval. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition The tool is described as getting 'detailed info about a specific block package from the registry' with instructions to 'use list_available_blocks first to find the block.' The verb 'get' and the action of retrieving information indicates a read-only query…
Attacks that exploit this kind of access
Get detailed info about a specific block package from the registry. Use list_available_blocks first to find the block. It is categorised as a Read tool in the Pl MCP Server, which means it retrieves data without modifying state.
Register the Pl MCP server in PolicyLayer and add a rule for get_block_info: 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 Pl. Nothing to install.
get_block_info 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_block_info 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_block_info. 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_block_info is provided by the Pl MCP server (@milaboratories/pl-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 →