Get the device type name from a device type Id
AI agents call get_device_type_name_from_id 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.
This tool performs a read-only query to resolve a device type identifier to its human-readable name. It has no side effects, does not modify device state, and does not trigger any commands or operations. It is purely informational, similar to other Read category tools on this server like get_cluster_name_from_id and get_cluster_id_from_name.
From the tool's definition Tool description states 'Get the device type name from a device type Id' — a straightforward lookup operation that retrieves descriptive metadata without modifying state or triggering side effects.
Documented attack patterns abuse exactly the kind of access get_device_type_name_from_id 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_device_type_name_from_id:
{
"version": "1",
"default": "deny",
"tools": {
"get_device_type_name_from_id": {}
}
}get_device_type_name_from_id 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 the device type name from a device type Id. 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_device_type_name_from_id: 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_device_type_name_from_id 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_device_type_name_from_id 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_device_type_name_from_id. 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_device_type_name_from_id 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.