requirements_create

THE RISK

Medium Risk

Why requirements_create needs a policy

This tool creates new requirements, which is a reversible data modification operation. It falls under Write category as it adds new records to the system without deleting or executing arbitrary operations.

From the tool's definition Tool name 'requirements_create' and description 'Create requirement' indicate the tool creates new data entries in the Testomatio platform.

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

POLICY

How to control requirements_create

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

policy.json

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

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

Create a free account and register Testomatio MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Testomatio MCP Server tools

Destructive requirements_delete Delete requirement (/api/v2/{project_id}/requirements/{id}) Write requirements_update Update requirement (/api/v2/{project_id}/requirements/{id}) Read analytics_stats Enterprise analytics: fetch an aggregated analytics report (/api/v2/{project_id}/analytics Read analytics_tests Enterprise analytics: list tests matching an analytics report (/api/v2/{project_id}/analyt Read milestones_get Get milestone by ID Read milestones_list List milestones (/api/v2/{project_id}/milestones) Read requirements_get Get requirement by ID Read requirements_list List requirements (/api/v2/{project_id}/requirements)

All 10 Testomatio MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about requirements_create

What does the requirements_create tool do? +

Create requirement (/api/v2/{project_id}/requirements). It is categorised as a Write tool in the Testomatio 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 requirements_create? +

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

What risk level is requirements_create? +

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

Can I rate-limit requirements_create? +

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

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

requirements_create is provided by the Testomatio MCP Server MCP server (testomatio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Testomatio MCP Server tool call.

Start from Testomatio MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →