requirements_get

THE RISK

Low Risk

Why requirements_get needs a policy

The tool retrieves a single requirement object by its identifier. There is no indication of data modification, deletion, execution of external operations, or financial transactions. This is a simple read operation typical of data retrieval from a test management system. The low severity reflects minimal risk if misused by an agent—it can only retrieve existing data without causing harm.

From the tool's definition Tool name 'requirements_get' and description 'Get requirement by ID' indicate a retrieval operation with no modifications or side effects. This is a straightforward query operation on a test management platform.

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

POLICY

How to control requirements_get

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_get:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "requirements_get": {}
  }
}

requirements_get is read-only, so it stays allowed — but 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.

CAP 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_create Create requirement (/api/v2/{project_id}/requirements) 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_list List requirements (/api/v2/{project_id}/requirements)

All 10 Testomatio MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about requirements_get

What does the requirements_get tool do? +

Get requirement by ID. It is categorised as a Read tool in the Testomatio MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on requirements_get? +

Register the Testomatio MCP Server MCP server in PolicyLayer and add a rule for requirements_get: 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_get? +

requirements_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit requirements_get? +

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

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

requirements_get 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 →