AI agents call get_node to retrieve information from Matter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention and context from sibling tools, 'get_node' most likely retrieves information about a specific Matter node/device. Retrieving node metadata is a read operation with no side effects. Confidence is moderate (0.7) due to empty description, but the naming pattern and server context strongly suggest a lookup/query function.
From the tool's definition Tool name 'get_node' with no description; sibling tools like 'get_nodes', 'get_cluster_name_from_id', 'get_device_type_name_from_id' are all read/lookup operations. The prefix 'get_' indicates retrieval without modification.
Documented attack patterns abuse exactly the kind of access get_node gives an agent:
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_node:
{
"version": "1",
"default": "deny",
"tools": {
"get_node": {}
}
}get_node is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_node. It is categorised as a Read tool in the Matter MCP Server, which means it retrieves data without modifying state.
Register the Matter MCP server in PolicyLayer and add a rule for get_node: 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.
get_node is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_node 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.
Set action: deny in the PolicyLayer policy for get_node. 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.
get_node 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.
Start from Matter, 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.
15 Matter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.