get_contract_events
Get events emitted by a smart contract.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/get-contract-events.md
What get_contract_events does on Aibtc
AI agents call get_contract_events to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_contract_events is rated Low
This tool retrieves historical or current event logs from a smart contract, which is a read-only query operation. It does not execute transactions, modify state, delete data, or commit financial obligations. The blast radius of misuse is minimal—an attacker could only gain visibility into past contract events, which are typically public blockchain data.
From the tool's definition Tool name and description: 'Get events emitted by a smart contract.' The verb 'Get' and the passive construction 'emitted by' indicate data retrieval with no modification or execution of contract logic.
Attacks that exploit this kind of access
The rule that runs get_contract_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_contract_events, this is the rule to start with:
get_contract_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every get_contract_events call is checked against it from then on.
Questions about get_contract_events
Get events emitted by a smart contract. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for get_contract_events: 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 Aibtc. Nothing to install.
get_contract_events 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_contract_events 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_contract_events. 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_contract_events is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue