๐ SETUP: List all repositories currently managed by Lspace.
AI agents call lspace_list_repositories to retrieve information from Lspace MCP Server without modifying anything โ typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about repositories without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk if misused by an AI agent โ at worst, an agent learns what repositories exist, which is informational only.
From the tool's definition Tool name 'lspace_list_repositories' with description 'List all repositories currently managed by Lspace' โ the verb 'list' and the operation of retrieving/enumerating existing repositories without modification indicates a read-only query operation.
Documented attack patterns abuse exactly the kind of access lspace_list_repositories gives an agent:
PolicyLayer is an MCP gateway โ it sits between your AI agents and Lspace MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for lspace_list_repositories:
{
"version": "1",
"default": "deny",
"tools": {
"lspace_list_repositories": {}
}
} lspace_list_repositories 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.
๐ SETUP: List all repositories currently managed by Lspace. It is categorised as a Read tool in the Lspace MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lspace MCP Server MCP server in PolicyLayer and add a rule for lspace_list_repositories: 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 Lspace MCP Server. Nothing to install.
lspace_list_repositories 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 lspace_list_repositories 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 lspace_list_repositories. 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.
lspace_list_repositories is provided by the Lspace MCP Server MCP server (lspace-io/lspace-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lspace MCP Server, 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.
7 Lspace MCP Server tools catalogued and risk-classified โ across an index of 43,000+ MCP servers.