get_contract_events

Get events emitted by a smart contract

SERVERStacks AI MCP Server SOURCEstack-ai-mcp/stacks-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/get-contract-events.md

WHAT IT DOES

What get_contract_events does on Stacks AI MCP Server

AI agents call get_contract_events to retrieve information from Stacks AI MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_contract_events is rated Low

This tool retrieves historical event logs from smart contracts, which is a read-only operation with no side effects. It does not create, modify, delete, or execute code. Even in a DeFi context with financial instruments, querying events is purely informational and poses minimal risk of misuse by an AI agent.

From the tool's definition Tool name 'get_contract_events' and description 'Get events emitted by a smart contract' indicate a retrieval operation that queries blockchain data without modifying state or executing transactions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_contract_events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Stacks AI MCP Server, 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 Allowed

get_contract_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_contract_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stacks AI MCP Server, apply this rule, and every get_contract_events call is checked against it from then on.

FAQ

Questions about get_contract_events

What does the get_contract_events tool do? +

Get events emitted by a smart contract. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_contract_events? +

Register the Stacks AI MCP Server 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 Stacks AI MCP Server. Nothing to install.

What risk level is get_contract_events? +

get_contract_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_contract_events? +

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.

How do I block get_contract_events completely? +

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.

What MCP server provides get_contract_events? +

get_contract_events is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Stacks AI MCP Server, and thousands of servers like it.

This server

All 200 Stacks AI MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →