get event selector
AI agents call event-sig to retrieve information from Blockchain MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries blockchain event selectors—static metadata about event signatures. It is purely informational with no side effects, no code execution, no state modification, and no financial impact. The operation is read-only and returns data needed for decoding blockchain events. Given the context of sibling tools like 'abi-decode', 'get-balance', and 'keccak256', this fits the pattern of data retrieval utilities.
From the tool's definition The tool is named 'event-sig' and described as 'get event selector'. This retrieves event signature information from blockchain data without modifying, executing code, or moving funds.
Attacks that exploit this kind of access
get event selector. It is categorised as a Read tool in the Blockchain MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blockchain MCP Server MCP server in PolicyLayer and add a rule for event-sig: 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 Blockchain MCP Server. Nothing to install.
event-sig 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 event-sig 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 event-sig. 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.
event-sig is provided by the Blockchain MCP Server MCP server (lienhage/blockchain-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 →