get_bot_matches

Get bot match history (trigger events) with pagination and search

SERVERinstantKOM MCP Server SOURCEinstantkom/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/instantkom-mcp-server/get-bot-matches.md

WHAT IT DOES

What get_bot_matches does on instantKOM MCP Server

AI agents call get_bot_matches to retrieve information from instantKOM 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_bot_matches is rated Low

This tool retrieves historical data about bot trigger events without modifying, creating, or deleting any information. It is a pure read operation with no side effects, making it a Read category risk with low severity since data exposure depends on what bot history contains but the tool itself performs only queries.

From the tool's definition Tool description states 'Get bot match history' with 'pagination and search', indicating data retrieval operations. The verb 'Get' and the absence of modification or deletion language confirm read-only functionality.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_bot_matches safely

PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_bot_matches, this is the rule to start with:

get_bot_matches Allowed

get_bot_matches 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_bot_matches": {}
  }
}

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

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

FAQ

Questions about get_bot_matches

What does the get_bot_matches tool do? +

Get bot match history (trigger events) with pagination and search. It is categorised as a Read tool in the instantKOM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_bot_matches? +

Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for get_bot_matches: 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 instantKOM MCP Server. Nothing to install.

What risk level is get_bot_matches? +

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

Can I rate-limit get_bot_matches? +

Yes. Add a rate_limit block to the get_bot_matches 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_bot_matches completely? +

Set action: deny in the PolicyLayer policy for get_bot_matches. 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_bot_matches? +

get_bot_matches is provided by the instantKOM MCP Server MCP server (instantkom/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 instantKOM MCP Server, and thousands of servers like it.

This server

All 245 instantKOM 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 →