π CREATE: Add content for automatic knowledge base generation. This is the PRIMARY tool for adding ANY content to lspace. Example: repositoryId=
AI agents use lspace_add_content to create or update resources in Lspace MCP Server β usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lspace MCP Server environment.
This tool creates new content entries in the knowledge base. While it modifies persistent data, the operation is reversible (as evidenced by the sibling tool 'lspace_undo_knowledge_base_changes'), making it a Write operation rather than Destructive.
From the tool's definition Tool description explicitly states 'CREATE: Add content' and 'PRIMARY tool for adding ANY content to lspace', indicating it creates or modifies data in the knowledge base.
Documented attack patterns abuse exactly the kind of access lspace_add_content 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_add_content:
{
"version": "1",
"default": "deny",
"tools": {
"lspace_add_content": {
"limits": [
{
"counter": "lspace_add_content_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} lspace_add_content stays usable, but capped β an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
π CREATE: Add content for automatic knowledge base generation. This is the PRIMARY tool for adding ANY content to lspace. Example: repositoryId=. It is categorised as a Write tool in the Lspace MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lspace MCP Server MCP server in PolicyLayer and add a rule for lspace_add_content: 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_add_content is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lspace_add_content 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_add_content. 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_add_content 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.