get_contract_log_events
Get smart contract log events with filtering
This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/get-contract-log-events.md
What get_contract_log_events does on Stacks AI MCP Server
AI agents call get_contract_log_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.
Why get_contract_log_events is rated Low
This tool retrieves and queries historical log events from smart contracts. It performs no state modification, deletion, execution of operations, or financial transactions. Filtering is a standard read operation. The low severity reflects that event log queries have minimal blast radius—an AI agent misusing this tool could at worst spam queries or expose public blockchain data already visible on-chain.
From the tool's definition Tool name 'get_contract_log_events' and description 'Get smart contract log events with filtering' indicate data retrieval with no side effects. The verb 'Get' combined with 'filtering' confirms read-only query operations on existing contract logs.
Attacks that exploit this kind of access
The rule that runs get_contract_log_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_log_events, this is the rule to start with:
get_contract_log_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 Stacks AI MCP Server, apply this rule, and every get_contract_log_events call is checked against it from then on.
Questions about get_contract_log_events
Get smart contract log events with filtering. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for get_contract_log_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.
get_contract_log_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_log_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_log_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_log_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.
More on Stacks AI MCP Server, and thousands of servers like it.
This server
Across the catalogue