AI agents use subscribe_to_task to create or update resources in Phabricator MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Phabricator MCP Server environment.
Based on the tool name and the server context (Phabricator task management), subscribing to a task typically adds a user as a subscriber/watcher, which is a reversible write operation with low blast radius. The sibling tool 'subscribe_to_differential' suggests a consistent pattern. Confidence is lowered due to the empty description.
From the tool's definition Tool name 'subscribe_to_task'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access subscribe_to_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Phabricator MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for subscribe_to_task:
{
"version": "1",
"default": "deny",
"tools": {
"subscribe_to_task": {
"limits": [
{
"counter": "subscribe_to_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}subscribe_to_task 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.
Free to start. No card required.
subscribe_to_task. It is categorised as a Write tool in the Phabricator MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Phabricator MCP Server MCP server in PolicyLayer and add a rule for subscribe_to_task: 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 Phabricator MCP Server. Nothing to install.
subscribe_to_task 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 subscribe_to_task 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 subscribe_to_task. 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.
subscribe_to_task is provided by the Phabricator MCP Server MCP server (yushengauggie/phabricator-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Phabricator 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.
11 Phabricator MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.