directory
Lookup contact and group IDs (self, peers, groups) for supported chat channels
This record as markdown: /tools/openclaw/directory.md
What directory does on OpenClaw
AI agents call directory to retrieve information from OpenClaw without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why directory is rated Low
The tool performs a directory lookup to retrieve contact and group identifiers. This is a read-only operation with no data modification, execution, or financial implications. Misuse risk is low as it only exposes contact/group metadata.
From the tool's definition 'Lookup contact and group IDs (self, peers, groups)' — purely retrieves/queries identity information with no side effects
Attacks that exploit this kind of access
The rule that runs directory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OpenClaw, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For directory, this is the rule to start with:
directory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OpenClaw, apply this rule, and every directory call is checked against it from then on.
Questions about directory
Lookup contact and group IDs (self, peers, groups) for supported chat channels. It is categorised as a Read tool in the OpenClaw MCP Server, which means it retrieves data without modifying state.
Register the OpenClaw MCP server in PolicyLayer and add a rule for directory: 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 OpenClaw. Nothing to install.
directory 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 directory 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 directory. 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.
directory is provided by the OpenClaw MCP server (openclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OpenClaw, and thousands of servers like it.
This server
Across the catalogue