使用 DoWhy GCM 创建Sklearn分类器包装器
AI agents use create_sklearn_classifier_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 a new classifier wrapper object in memory. This is a Write operation (object creation), but its blast radius is low since it only instantiates a model wrapper with no external side effects, data deletion, code execution, or financial implications. Confidence is slightly reduced because the description is in Chinese and minimal, limiting certainty about full behavior.
From the tool's definition create_sklearn_classifier_gcm — 'create' indicates instantiation of a new object (a Sklearn classifier wrapper via DoWhy GCM)
Attacks that exploit this kind of access
使用 DoWhy GCM 创建Sklearn分类器包装器. 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_sklearn_classifier_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_sklearn_classifier_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_sklearn_classifier_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_sklearn_classifier_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_sklearn_classifier_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 →