mechanism_attribution

使用 DoWhy 进行机制归因

Server DoWhy MCP v2 0 lesong36/dowhy_mcp
Category Write
Risk class Medium
Parameters 00 required

What mechanism_attribution does on DoWhy MCP v2 0

AI agents use mechanism_attribution 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.

Why mechanism_attribution needs a policy

An AI agent can call mechanism_attribution faster than any human can review — one bad instruction and it creates or modifies resources in DoWhy MCP v2 0 by the hundred, each call as confident as the last.

Questions about mechanism_attribution

What does the mechanism_attribution tool do? +

使用 DoWhy 进行机制归因. 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.

How do I enforce a policy on mechanism_attribution? +

Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for mechanism_attribution: 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.

What risk level is mechanism_attribution? +

mechanism_attribution is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mechanism_attribution? +

Yes. Add a rate_limit block to the mechanism_attribution 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.

How do I block mechanism_attribution completely? +

Set action: deny in the PolicyLayer policy for mechanism_attribution. 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.

What MCP server provides mechanism_attribution? +

mechanism_attribution 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.