Medium Risk

create_api

create_api

How to control create_api ↓

What create_api does on Amazon Redshift MCP Server

AI agents use create_api to create or update resources in Amazon Redshift MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon Redshift MCP Server environment.

Medium Risk

Why create_api needs a policy

The tool name 'create_api' implies creating a new API resource, which is a Write operation. However, the empty description severely limits confidence. It could potentially be Execute or higher severity depending on what 'create_api' does in the Redshift context. Based on name alone, Write is the most reasonable classification, but confidence is low.

From the tool's definition Tool name 'create_api' suggests creation of an API resource, which is a write operation. Description is empty and uninformative.

Documented attack patterns abuse exactly the kind of access create_api gives an agent:

How to control create_api

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Redshift MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_api:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_api": {
      "limits": [
        {
          "counter": "create_api_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_api 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.

  1. Create a free account and register Amazon Redshift MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_api

What does the create_api tool do? +

create_api. It is categorised as a Write tool in the Amazon Redshift MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_api? +

Register the Amazon Redshift MCP Server MCP server in PolicyLayer and add a rule for create_api: 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 Amazon Redshift MCP Server. Nothing to install.

What risk level is create_api? +

create_api is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_api? +

Yes. Add a rate_limit block to the create_api 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.

How do I block create_api completely? +

Set action: deny in the PolicyLayer policy for create_api. 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.

What MCP server provides create_api? +

create_api is provided by the Amazon Redshift MCP Server MCP server (awslabs.redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Redshift MCP Server tool call.

Start from Amazon Redshift 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.

805 Amazon Redshift MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.