Create a new namespace in an S3 table bucket. Creates a namespace. A namespace is a logical grouping of tables within your S3 table bucket, which you can use to organize S3 tables. Permissions: You must have the s3tables:CreateNamespace permission to use this operation.
AI agents use create_namespace to create or update resources in AWS — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS environment.
This tool creates a new namespace resource within an S3 table bucket, which is a reversible write operation. It does not execute arbitrary code, delete data, move money, or perform read-only queries. The severity is medium because misconfiguration or unauthorized namespace creation could affect data organization and access patterns in S3, but the operation itself is not destructive and can be undone or managed.
From the tool's definition Tool description states 'Create a new namespace' and 'Creates a namespace.' This is a create operation that modifies the organizational structure of S3 table buckets by adding a new namespace resource.
Documented attack patterns abuse exactly the kind of access create_namespace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS, and nothing reaches the server without passing your rules. This is the rule we recommend for create_namespace:
{
"version": "1",
"default": "deny",
"tools": {
"create_namespace": {
"limits": [
{
"counter": "create_namespace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_namespace 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 a new namespace in an S3 table bucket. Creates a namespace. A namespace is a logical grouping of tables within your S3 table bucket, which you can use to organize S3 tables. Permissions: You must have the s3tables:CreateNamespace permission to use this operation. It is categorised as a Write tool in the AWS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS MCP server in PolicyLayer and add a rule for create_namespace: 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 AWS. Nothing to install.
create_namespace 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_namespace 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_namespace. 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_namespace is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS, 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.
300 AWS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.