// SCAN REPORT

Binelek MCP Server

22 tools. 8 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 3 Jul 2026

8 can modify or destroy data

14 read-only

22 tools total

Community server · catalogue entry verified 03/07/2026

How to control Binelek MCP Server ↓

TOOL MAP

What Binelek MCP Server exposes to your agents

Read (14) Write / Execute (7) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Binelek MCP Server tools

Destructive · High binelek_delete_entity This tool permanently removes data from the knowledge graph without a reversible operation. Execute · High binelek_trigger_pipeline Triggering pipeline execution is an Execute action because it initiates automated processes whose side effects (data processing, transformations, external API calls, etc.) are dependent on the pipeline's configuration an Execute · High binelek_generate_code This tool triggers an external code generation service (Binah.Regen) that produces and likely writes code artifacts (DTOs, validators, repositories, GraphQL schemas) based on an input file. Execute · High binelek_ai_predict This tool executes ML model inference pipelines on the Binelek platform.

8 of Binelek MCP Server's 22 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Binelek MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Binelek MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "binelek_delete_entity": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "binelek_create_entity": {
    "limits": [
      {
        "counter": "binelek_create_entity_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "binelek_ai_analyze_entity": {
    "limits": [
      {
        "counter": "binelek_ai_analyze_entity_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Binelek MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON BINELEK →

Instant setup, no code required.

FULL CATALOGUE

All 22 Binelek MCP Server tools

DESTRUCTIVE 1 tools

Destructive binelek_delete_entity Delete an entity from the knowledge graph. This will also remove all relationships connected to this entity.

EXECUTE 4 tools

Execute binelek_ai_predict Make predictions using trained ML models. Available models include: cost_forecasting, property_valuation, mark Execute binelek_generate_code Generate code from an ontology YAML file. The Binah.Regen service generates DTOs, validators, repositories, Gr Execute binelek_query_entities Execute a Cypher query against the Binelek Neo4j knowledge graph. Use this for complex graph traversals, patte Execute binelek_trigger_pipeline Manually trigger a pipeline execution. This will start an immediate run of the pipeline with optional paramete

WRITE 3 tools

Write binelek_create_entity Create a new entity in the Binelek knowledge graph. The entity will be validated against the ontology schema a Write binelek_create_relationship Create a relationship between two entities in the knowledge graph. Write binelek_update_entity Update an existing entity in the knowledge graph. Only provided attributes will be updated, others remain unch

READ 14 tools

Read binelek_ai_analyze_entity Analyze a specific entity using AI. Provides insights, anomaly detection, recommendations, and risk assessment Read binelek_ai_chat Chat with the Binelek AI assistant. The AI has access to the knowledge graph and can answer questions, provide Read binelek_get_domain Get detailed configuration for a specific domain including metadata, pricing, and market analysis. Read binelek_get_entity Get a specific entity from the Binelek knowledge graph by its ID. Returns all properties and metadata for the Read binelek_get_ontology_schema Get the complete ontology schema for a domain. This includes all entity types, relationships, properties, and Read binelek_get_pipeline Get details about a specific pipeline including its configuration, schedule, and status. Read binelek_get_pipeline_runs Get the execution history for a specific pipeline. Shows all runs with their status, duration, and results. Read binelek_get_relationships Get all relationships connected to a specific entity. Returns both incoming and outgoing relationships with th Read binelek_hybrid_search Combine semantic and keyword search for best results. This uses both vector similarity and keyword matching wi Read binelek_keyword_search Perform keyword-based search using Elasticsearch. This provides exact matches and supports filters for structu Read binelek_list_domains List all available domain configurations. Binelek supports multiple industry verticals (Real Estate, Healthcar Read binelek_list_pipelines List all available data pipelines in the Binelek platform. Pipelines handle ETL operations, data ingestion fro Read binelek_semantic_search Perform semantic search across the knowledge graph using vector embeddings. This finds entities based on meani Read binelek_validate_yaml Validate an ontology YAML configuration file against the Binelek schema. This checks syntax, structure, and bu

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Binelek MCP Server

Can an AI agent delete data through the Binelek MCP Server MCP server? +

Yes. The Binelek MCP Server server exposes 1 destructive tools including binelek_delete_entity. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Binelek MCP Server? +

The Binelek MCP Server server has 3 write tools including binelek_create_entity, binelek_create_relationship, binelek_update_entity. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Binelek MCP Server.

How many tools does the Binelek MCP Server MCP server expose? +

22 tools across 4 categories: Destructive, Execute, Read, Write. 14 are read-only. 8 can modify, create, or delete data.

How do I enforce a policy on Binelek MCP Server? +

Register the Binelek MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Binelek MCP Server tool call.

Deterministic rules across all 22 Binelek MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BINELEK →

Instant setup, no code required.

22 Binelek MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.