Low Risk

check_compatibility

Check if a dataset

How to control check_compatibility ↓

What check_compatibility does on MobusMCP

AI agents call check_compatibility to retrieve information from MobusMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why check_compatibility needs a policy

This tool retrieves compatibility information about datasets without creating, modifying, deleting, executing code, or committing financial resources. It appears to be a Read operation that queries dataset metadata to inform users about compatibility constraints.

From the tool's definition The tool name 'check_compatibility' combined with the server's stated functions of 'search, preview, and analyze datasets' indicates a query/assessment operation.

Documented attack patterns abuse exactly the kind of access check_compatibility gives an agent:

How to control check_compatibility

PolicyLayer is an MCP gateway — it sits between your AI agents and MobusMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for check_compatibility:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_compatibility": {}
  }
}

check_compatibility is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MobusMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about check_compatibility

What does the check_compatibility tool do? +

Check if a dataset. It is categorised as a Read tool in the MobusMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_compatibility? +

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

What risk level is check_compatibility? +

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

Can I rate-limit check_compatibility? +

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

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

check_compatibility is provided by the Mobus MCP server (mobus-ai/mobus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MobusMCP tool call.

Start from MobusMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

13 MobusMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.