Low Risk

get_issues_by_severity

Get all issues of a specific severity level.

How to control get_issues_by_severity ↓

What get_issues_by_severity does on Tech Debt MCP Server

AI agents call get_issues_by_severity to retrieve information from Tech Debt MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_issues_by_severity needs a policy

This tool queries and returns issues filtered by severity—a read-only operation that retrieves data without creating, modifying, or deleting anything. No external code execution or state changes occur. Low severity because misuse poses minimal risk: an agent might over-query or access sensitive issue data, but cannot alter systems or trigger unintended actions.

From the tool's definition Tool name 'get_issues_by_severity' and description 'Get all issues of a specific severity level' indicate a retrieval operation with no side effects.

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

How to control get_issues_by_severity

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_issues_by_severity": {}
  }
}

get_issues_by_severity is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tech Debt 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_issues_by_severity

What does the get_issues_by_severity tool do? +

Get all issues of a specific severity level. It is categorised as a Read tool in the Tech Debt MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_issues_by_severity? +

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

What risk level is get_issues_by_severity? +

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

Can I rate-limit get_issues_by_severity? +

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

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

get_issues_by_severity is provided by the Tech Debt MCP Server MCP server (pierrejanineh/techdebtmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tech Debt MCP Server tool call.

Start from Tech Debt 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.

16 Tech Debt 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.