github_issue_track
Track and manage issues Use when native Bash / file tools are wrong because this MCP tool exposes Ruflo-specific state or controllers that have no shell equivalent. For tasks that fit a one-line native command, prefer that.
This record as markdown: /tools/hamza-agent-hub-252/github-issue-track.md
What github_issue_track does on Hamza Agent Hub 252
AI agents use github_issue_track to create or update resources in Hamza Agent Hub 252, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hamza Agent Hub 252 environment.
Why github_issue_track is rated Medium
Issue tracking typically involves creating new issues, updating status/assignments, adding comments, or modifying metadata—all reversible write operations. While the description is somewhat vague and doesn't explicitly detail what 'manage' entails, the verb 'manage' combined with 'track' strongly implies write capability.
From the tool's definition Tool name 'github_issue_track' and description stating 'Track and manage issues' indicates creation, modification, or state changes to issue records. The phrase 'manage issues' suggests write operations beyond read-only queries.
Attacks that exploit this kind of access
The rule that runs github_issue_track safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hamza Agent Hub 252, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_issue_track, this is the rule to start with:
github_issue_track stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hamza Agent Hub 252, apply this rule, and every github_issue_track call is checked against it from then on.
Questions about github_issue_track
Track and manage issues Use when native Bash / file tools are wrong because this MCP tool exposes Ruflo-specific state or controllers that have no shell equivalent. For tasks that fit a one-line native command, prefer that. It is categorised as a Write tool in the Hamza Agent Hub 252 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for github_issue_track: 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 Hamza Agent Hub 252. Nothing to install.
github_issue_track is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the github_issue_track 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 github_issue_track. 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.
github_issue_track is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hamza Agent Hub 252, and thousands of servers like it.
This server
Across the catalogue