Low Risk

issue_tracker_help

issue_tracker_help

How to control issue_tracker_help ↓

What issue_tracker_help does on Claude Team MCP Server

AI agents call issue_tracker_help as a supporting operation in Claude Team MCP Server workflows.

Low Risk

Why issue_tracker_help needs a policy

The description is completely empty, providing no information about what this tool does. The name 'issue_tracker_help' suggests it might provide help/documentation about an issue tracker, which would be a Read operation, but without any description we cannot be certain. Given the context of a Claude Team MCP Server focused on orchestrating sessions and worktrees, this tool seems out of place.

From the tool's definition Tool name is 'issue_tracker_help' and description is empty or uninformative.

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

How to control issue_tracker_help

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "issue_tracker_help": {
      "limits": [
        {
          "counter": "issue_tracker_help_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

issue_tracker_help gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude Team 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.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about issue_tracker_help

What does the issue_tracker_help tool do? +

issue_tracker_help. It is categorised as a Other tool in the Claude Team MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on issue_tracker_help? +

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

What risk level is issue_tracker_help? +

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

Can I rate-limit issue_tracker_help? +

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

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

issue_tracker_help is provided by the Claude Team MCP Server MCP server (martian-engineering/maniple). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Team MCP Server tool call.

Start from Claude Team 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 Claude Team 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.