This record as markdown: /tools/io-github-portel-dev-ncp/create-keyspace.md
What create_keyspace does on Ncp
AI agents use create_keyspace to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why create_keyspace is rated Medium
Creating a keyspace modifies the database schema in a way that persists and affects all subsequent operations within that namespace. While not destructive (deletion would be Destructive), it is a Write operation that creates persistent infrastructure.
From the tool's definition Tool name 'create_keyspace' and description 'Create Cassandra keyspace' indicate irreversible creation of a database namespace. Cassandra keyspaces are persistent database structures that organize tables and replication settings.
Attacks that exploit this kind of access
The rule that runs create_keyspace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_keyspace, this is the rule to start with:
create_keyspace 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every create_keyspace call is checked against it from then on.
Questions about create_keyspace
Create Cassandra keyspace. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for create_keyspace: 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 Ncp. Nothing to install.
create_keyspace 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 create_keyspace 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 create_keyspace. 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.
create_keyspace is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue