create_feature_spec · Rampify MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_feature_spec does on Rampify MCP Server

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

WHY IT NEEDS A POLICY

Why create_feature_spec needs a policy

This is a Write operation because it creates and saves data (feature specifications) to a backend service. The severity is medium rather than high because feature specs are reversible (can typically be updated or deleted), affect configuration/planning rather than production systems or financial data, and the impact is limited to the user's Rampify account.

From the tool's definition Tool description states 'Create and save a feature specification' — this performs a create operation that modifies data. The instruction emphasizes that Claude must generate the spec before calling, indicating the tool persists data to Rampify.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_feature_spec Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_feature_spec": {
      "limits": [
        {
          "counter": "create_feature_spec_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Rampify MCP Server, so you can run agents against it safely.

FAQ

Questions about create_feature_spec

What does the create_feature_spec tool do? +

Create and save a feature specification to Rampify. IMPORTANT: Before calling this tool, YOU (Claude) must generate the complete structured spec from the user. It is categorised as a Write tool in the Rampify 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_feature_spec? +

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

What risk level is create_feature_spec? +

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

Can I rate-limit create_feature_spec? +

Yes. Add a rate_limit block to the create_feature_spec 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_feature_spec completely? +

Set action: deny in the PolicyLayer policy for create_feature_spec. 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_feature_spec? +

create_feature_spec is provided by the Rampify MCP Server MCP server (rampify-dev/rampify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.