This record as markdown: /tools/io-github-aibtcdev-mcp-server/competition-allowlist.md
What competition_allowlist does on Aibtc
AI agents call competition_allowlist 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 competition_allowlist is rated Low
The tool name 'competition_allowlist' combined with the partial description 'Get the set of' strongly suggests a read operation that retrieves allowlist entries. No write, execute, or destructive indicators are present. Confidence is reduced due to the truncated description.
From the tool's definition 'Get the set of' — description appears truncated but begins with a read/retrieval verb
Attacks that exploit this kind of access
The rule that runs competition_allowlist 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 competition_allowlist, this is the rule to start with:
competition_allowlist 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 competition_allowlist call is checked against it from then on.
Questions about competition_allowlist
Get the set of \. 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 competition_allowlist: 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.
competition_allowlist 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 competition_allowlist 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 competition_allowlist. 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.
competition_allowlist 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