Estimate credit cost for a conversion BEFORE running it. Returns word count, page calculation (300 words/page), and a credit breakdown by format and template type. Use this when the user asks 'how much will this cost?' or when you suspect a conversion might exceed their balance — convert_document...
Risk signalsAccepts raw HTML/template content (content)
Part of the Mdmagic Mcp Server server.
Free to start. No card required.
AI agents invoke estimate_conversion_cost to trigger processes or run actions in Mdmagic Mcp Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
estimate_conversion_cost can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"estimate_conversion_cost": {
"limits": [
{
"counter": "estimate_conversion_cost_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Mdmagic Mcp Server policy for all 10 tools.
These attack patterns abuse exactly the kind of access estimate_conversion_cost gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Estimate credit cost for a conversion BEFORE running it. Returns word count, page calculation (300 words/page), and a credit breakdown by format and template type. Use this when the user asks 'how much will this cost?' or when you suspect a conversion might exceed their balance — convert_document refuses to run if credits are insufficient, so estimating first is friendlier.. It is categorised as a Execute tool in the Mdmagic Mcp Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mdmagic Mcp Server MCP server in PolicyLayer and add a rule for estimate_conversion_cost: 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 Mdmagic Mcp Server. Nothing to install.
estimate_conversion_cost is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the estimate_conversion_cost 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 estimate_conversion_cost. 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.
estimate_conversion_cost is provided by the Mdmagic Mcp Server MCP server (@mdmagic/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Mdmagic Mcp Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.