使用 DoWhy GCM 获取噪声依赖函数
AI agents call get_noise_dependent_function_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 retrieves or extracts a noise-dependent function from a Graphical Causal Model (GCM) structure. It is a read operation that queries model internals to obtain analytical artifacts. There are no side effects, irreversible changes, code execution, or financial implications. The function returned is a data structure used for further analysis, not an execution of that function.
From the tool's definition Tool name 'get_noise_dependent_function_gcm' and description 'retrieve noise-dependent function using DoWhy GCM' indicate a retrieval/query operation that returns a function object or function definition without modifying, deleting, or executing external…
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 get_noise_dependent_function_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.
get_noise_dependent_function_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 get_noise_dependent_function_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 get_noise_dependent_function_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.
get_noise_dependent_function_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 →