Search Matter protocol documentation on mattercoder.com
AI agents call search_matter_docs 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 retrieves information from external documentation. It is purely informational and read-only. No data is modified, deleted, or executed. Even in the context of a broader Matter server that includes device commands and commissioning, this specific tool performs only a search/lookup operation against static documentation.
From the tool's definition Tool name contains 'search' and description states 'Search Matter protocol documentation' — a retrieval operation with no side effects. Querying public documentation does not modify, delete, or execute code.
Documented attack patterns abuse exactly the kind of access search_matter_docs 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 search_matter_docs:
{
"version": "1",
"default": "deny",
"tools": {
"search_matter_docs": {}
}
}search_matter_docs 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.
Search Matter protocol documentation on mattercoder.com. 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 search_matter_docs: 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.
search_matter_docs 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 search_matter_docs 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 search_matter_docs. 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.
search_matter_docs 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.