inference_check_provider

Re-run the marketplace

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/inference-check-provider.md

WHAT IT DOES

What inference_check_provider does on Aibtc

AI agents invoke inference_check_provider to trigger actions in Aibtc. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why inference_check_provider is rated High

The description 'Re-run the marketplace' implies executing or triggering some marketplace process. This falls under Execute as it appears to trigger an external operation. However, the description is vague and uninformative, which lowers confidence.

From the tool's definition 'Re-run the marketplace' suggests triggering an external operation or process execution

Attacks that exploit this kind of access

RECOMMENDED RULE

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

inference_check_provider Rate-limited

inference_check_provider stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "inference_check_provider": {
      "limits": [
        {
          "counter": "inference_check_provider_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about inference_check_provider

What does the inference_check_provider tool do? +

Re-run the marketplace. It is categorised as a Execute tool in the Aibtc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on inference_check_provider? +

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

inference_check_provider is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit inference_check_provider? +

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

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

inference_check_provider 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →