使用 DoWhy GCM 检查节点是否为根节点
AI agents call is_root_node_gcm to retrieve information from DoWhy MCP v2 0 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a boolean check on a causal graph structure to determine if a node is a root node (has no incoming edges). This is a read-only operation that retrieves or queries structural properties of a causal model with no side effects, data modification, or external operations. The tool is consistent with causal inference analysis where examining graph topology is foundational analysis work.
From the tool's definition Tool name 'is_root_node_gcm' and description '使用 DoWhy GCM 检查节点是否为根节点' (Check if a node is a root node using DoWhy GCM) indicates a query/inspection operation that examines graph properties without modifying data or triggering external effects.
Attacks that exploit this kind of access
使用 DoWhy GCM 检查节点是否为根节点. It is categorised as a Read tool in the DoWhy MCP v2 0 MCP Server, which means it retrieves data without modifying state.
Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for is_root_node_gcm: 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 DoWhy MCP v2 0. Nothing to install.
is_root_node_gcm 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 is_root_node_gcm 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 is_root_node_gcm. 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.
is_root_node_gcm is provided by the DoWhy MCP v2 0 MCP server (lesong36/dowhy_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →