get_cluster_id_from_name

THE RISK

Low Risk

Why get_cluster_id_from_name needs a policy

This tool retrieves information (cluster ID) based on a query parameter (cluster name). It is purely informational and does not modify, execute, delete, or control any devices or data. The blast radius of misuse is minimal since the tool only returns reference data that is already exposed in the Matter protocol specification.

From the tool's definition Tool name 'get_cluster_id_from_name' and description 'Get the cluster Id from a cluster name' indicate a lookup operation that retrieves metadata. The function performs a simple mapping/query with no side effects.

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

POLICY

How to control get_cluster_id_from_name

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cluster_id_from_name": {}
  }
}

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

Create a free account and register Matter — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Matter tools

Execute start_listening Start listening for node events and changes. Execute commission_with_code Commission a new device using QR code or manual pairing code. Execute device_command Send a command to a device. Write set_thread_dataset Set Thread credentials for device commissioning. Write set_wifi_credentials Set WiFi credentials for device commissioning. Write write_attribute Write an attribute value to a node. Read get_cluster_commands get_cluster_commands Read get_cluster_name_from_id Get the cluster name from a cluster Id

All 15 Matter tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_cluster_id_from_name

What does the get_cluster_id_from_name tool do? +

Get the cluster Id from a cluster name. It is categorised as a Read tool in the Matter MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cluster_id_from_name? +

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

What risk level is get_cluster_id_from_name? +

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

Can I rate-limit get_cluster_id_from_name? +

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

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

get_cluster_id_from_name is provided by the Matter MCP server (mattercoder/matter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Matter tool call.

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

CHECK YOUR STACK →