get-test-steps

THE RISK

Low Risk

Why get-test-steps needs a policy

This tool retrieves or queries test step data from JIRA/Zephyr test tickets without creating, modifying, deleting, or executing any operations. It is a read-only operation with minimal security risk, as it only accesses existing test data.

From the tool's definition Tool name 'get-test-steps' and description 'Get test steps from a test ticket via Zephyr integration' indicate a retrieval operation with no modification or deletion of data.

Documented attack patterns abuse exactly the kind of access get-test-steps gives an agent:

POLICY

How to control get-test-steps

PolicyLayer is an MCP gateway — it sits between your AI agents and JIRA MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get-test-steps:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-test-steps": {}
  }
}

get-test-steps 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 JIRA MCP — 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 JIRA MCP tools

Write remove-watcher Remove a watcher from a JIRA ticket Write add-comment Add a comment to a JIRA ticket Write add-test-steps Add test steps to a test ticket via Zephyr integration Write add-watcher Add a watcher to a JIRA ticket Write assign-ticket Assign or unassign a JIRA ticket Write create-ticket Create a jira ticket Write link-tickets Link two jira tickets Write transition-ticket Transition a JIRA ticket to a different status

All 14 JIRA MCP 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 get-test-steps

What does the get-test-steps tool do? +

Get test steps from a test ticket via Zephyr integration. It is categorised as a Read tool in the JIRA MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-test-steps? +

Register the JIRA MCP server in PolicyLayer and add a rule for get-test-steps: 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 JIRA MCP. Nothing to install.

What risk level is get-test-steps? +

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

Can I rate-limit get-test-steps? +

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

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

get-test-steps is provided by the JIRA MCP server (mankowskinick/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every JIRA MCP tool call.

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

CHECK YOUR STACK →