// SCAN REPORT

MaStR MCP Server

21 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 28 Jun 2026

0 can modify or destroy data

21 read-only

21 tools total

Community server · catalogue entry verified 28/06/2026

How to control MaStR MCP Server ↓

TOOL MAP

What MaStR MCP Server exposes to your agents

Read (21) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control MaStR MCP Server

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

Cap read operations

{
  "get_actor": {
    "limits": [
      {
        "counter": "get_actor_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 MaStR 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 MASTR →

Instant setup, no code required.

FULL CATALOGUE

All 21 MaStR MCP Server tools

READ 21 tools

Read get_actor get_actor Read get_api_quota Check how many SOAP API calls have been used today vs. the daily limit. Read get_balancing_areas get_balancing_areas Read get_catalog_categories List all available MaStR catalog categories with their IDs. Read get_catalog_values get_catalog_values Read get_grid_connection get_grid_connection Read get_local_time Connection test — returns current server time if MaStR SOAP service is reachable. Read get_location get_location Read get_recent_changes get_recent_changes Read get_unit get_unit Read search_actors_public search_actors_public Read search_actors_soap search_actors_soap Read search_gas_consumption_public search_gas_consumption_public Read search_gas_consumption_soap search_gas_consumption_soap Read search_gas_production_public search_gas_production_public Read search_gas_production_soap search_gas_production_soap Read search_grid_connections_public search_grid_connections_public Read search_power_consumption_public search_power_consumption_public Read search_power_consumption_soap search_power_consumption_soap Read search_power_generation_public search_power_generation_public Read search_power_generation_soap search_power_generation_soap

FAQ

Questions about MaStR MCP Server

Is the MaStR MCP Server MCP server safe to use without restrictions? +

The MaStR MCP Server server is primarily read-only with 21 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

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

21 tools across 1 categories: Read. 21 are read-only. 0 can modify, create, or delete data.

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

Register the MaStR 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 MaStR MCP Server tool call.

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

ENFORCE POLICY ON MASTR →

Instant setup, no code required.

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