competition_status

Get the current AIBTC trading competition standing for an agent, with mark-to-current P&L computed locally. Latency note: by default this call also paginates the agent

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/competition-status.md

WHAT IT DOES

What competition_status does on Aibtc

AI agents call competition_status 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.

RISK

Why competition_status is rated Low

The tool retrieves and displays current competition standings and P&L (profit/loss) metrics for an agent. This is a read-only operation that queries existing data and performs local computation without making any state changes. The description explicitly states it 'gets' data and computes values locally, which are hallmarks of a Read category tool.

From the tool's definition Tool name 'competition_status' and description 'Get the current AIBTC trading competition standing for an agent, with mark-to-current P&L computed locally' indicates retrieval of competition standings and portfolio performance data with no modification,…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs competition_status 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_status, this is the rule to start with:

competition_status Allowed

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

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

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

FAQ

Questions about competition_status

What does the competition_status tool do? +

Get the current AIBTC trading competition standing for an agent, with mark-to-current P&L computed locally. Latency note: by default this call also paginates the agent. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on competition_status? +

Register the Aibtc MCP server in PolicyLayer and add a rule for competition_status: 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.

What risk level is competition_status? +

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

Can I rate-limit competition_status? +

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

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

competition_status 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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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