AI agents call get_differential_detailed to retrieve information from Phabricator MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the naming convention and context of sibling tools (which are clearly Read operations for retrieving task/review data) strongly suggest this tool retrieves detailed information about Phabricator differentials. It has no apparent capability to modify, delete, or execute operations.
From the tool's definition Tool name 'get_differential_detailed' indicates retrieval of differential (code review) information. Sibling tools like 'get_differential', 'get_task', and 'get_review_feedback' are all Read operations that query data without side effects.
Documented attack patterns abuse exactly the kind of access get_differential_detailed 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 get_differential_detailed:
{
"version": "1",
"default": "deny",
"tools": {
"get_differential_detailed": {}
}
}get_differential_detailed 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_differential_detailed. It is categorised as a Read tool in the Phabricator MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Phabricator MCP Server MCP server in PolicyLayer and add a rule for get_differential_detailed: 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.
get_differential_detailed 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_differential_detailed 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_differential_detailed. 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_differential_detailed 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.