Get all issues of a specific category.
AI agents call get_issues_by_category 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.
This tool queries and retrieves technical debt issues filtered by category. It performs no writes, deletions, code execution, or financial operations. The operation is purely informational—it returns data without altering state. The low severity reflects that misuse would only expose information already present in the analysis system, posing minimal risk even if accessed by an unauthorized agent.
From the tool's definition Tool name 'get_issues_by_category' and description 'Get all issues of a specific category' indicate retrieval/query operation with no modification or side effects. The verb 'get' and the read-only nature of filtering existing issues align with Read category.
Documented attack patterns abuse exactly the kind of access get_issues_by_category gives an agent:
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_category:
{
"version": "1",
"default": "deny",
"tools": {
"get_issues_by_category": {}
}
}get_issues_by_category is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all issues of a specific category. It is categorised as a Read tool in the Tech Debt MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tech Debt MCP Server MCP server in PolicyLayer and add a rule for get_issues_by_category: 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.
get_issues_by_category is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_issues_by_category 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.
Set action: deny in the PolicyLayer policy for get_issues_by_category. 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.
get_issues_by_category 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.
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.