Get event logs emitted by a contract address. Supports block range and
AI agents call event_logs to retrieve information from Kxcoscan AI Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Event logs are historical, immutable records on the blockchain. Querying them is a pure read operation with no ability to modify data, execute code, trigger external operations, or affect financial state. The tool is analogous to a search/fetch operation on a public ledger.
From the tool's definition Tool retrieves event logs emitted by a contract address with optional filtering by block range. The verb 'Get' and the read-only nature of querying historical blockchain data (event logs are immutable records) indicate no side effects or state mutations.
Attacks that exploit this kind of access
Get event logs emitted by a contract address. Supports block range and. It is categorised as a Read tool in the Kxcoscan AI Tools MCP Server, which means it retrieves data without modifying state.
Register the Kxcoscan AI Tools MCP server in PolicyLayer and add a rule for event_logs: 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 Kxcoscan AI Tools. Nothing to install.
event_logs 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_logs 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_logs. 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_logs is provided by the Kxcoscan AI Tools MCP server (keralpatel/kxcoscan-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 →