使用 DoWhy GCM 创建多项式回归器
AI agents use create_polynom_regressor_gcm to create or update resources in DoWhy MCP v2 0 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DoWhy MCP v2 0 environment.
The tool creates and configures a polynomial regression model object, which is a reversible data modification operation (Write category). The severity is low because creating a statistical model has minimal blast radius—the worst outcome is an incorrectly specified model, which can be discarded or overwritten without system compromise.
From the tool's definition Tool name contains 'create' and description states '创建多项式回归器' (create polynomial regressor). Creates a regressor object that is stored/configured but does not permanently delete, execute arbitrary code, or move financial assets.
Attacks that exploit this kind of access
使用 DoWhy GCM 创建多项式回归器. It is categorised as a Write tool in the DoWhy MCP v2 0 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for create_polynom_regressor_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.
create_polynom_regressor_gcm 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 create_polynom_regressor_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 create_polynom_regressor_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.
create_polynom_regressor_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 →