List all workspaces you are a member of (personal + shared).
AI agents call list_workspaces to retrieve information from Memlord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of workspace memberships without modifying, deleting, or executing any operations. It is a read-only information retrieval action with minimal security risk even if misused by an AI agent, as it only exposes metadata about workspace access already held by the authenticated user.
From the tool's definition Tool name 'list_workspaces' and description 'List all workspaces you are a member of' indicates a simple retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_workspaces gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memlord, and nothing reaches the server without passing your rules. This is the rule we recommend for list_workspaces:
{
"version": "1",
"default": "deny",
"tools": {
"list_workspaces": {}
}
} list_workspaces 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.
List all workspaces you are a member of (personal + shared). It is categorised as a Read tool in the Memlord MCP Server, which means it retrieves data without modifying state.
Register the Memlord MCP server in PolicyLayer and add a rule for list_workspaces: 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 Memlord. Nothing to install.
list_workspaces 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 list_workspaces 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 list_workspaces. 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.
list_workspaces is provided by the Memlord MCP server (myrikld/memlord). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memlord, 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.
10 Memlord tools catalogued and risk-classified — across an index of 43,000+ MCP servers.