High Risk →

transform_card

Transform an Adaptive Card: upgrade/downgrade version, apply host-specific constraints, or flatten nesting.

Part of the Adaptive Cards MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

adaptive-cards-mcp Execute Risk 3/5

AI agents invoke transform_card to trigger processes or run actions in Adaptive Cards. 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.

transform_card can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept 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.

io-github-vikrantsingh01-adaptive-cards-mcp.yaml
tools:
  transform_card:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Adaptive Cards policy for all 9 tools.

Tool Name transform_card
Category Execute
Risk Level High

View all 9 tools →

Agents calling execute-class tools like transform_card have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

transform_card is one of the high-risk operations in Adaptive Cards. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the transform_card tool do? +

Transform an Adaptive Card: upgrade/downgrade version, apply host-specific constraints, or flatten nesting.. It is categorised as a Execute tool in the Adaptive Cards MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on transform_card? +

Add a rule in your Intercept YAML policy under the tools section for transform_card. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Adaptive Cards MCP server.

What risk level is transform_card? +

transform_card is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit transform_card? +

Yes. Add a rate_limit block to the transform_card rule in your Intercept 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 transform_card completely? +

Set action: deny in the Intercept policy for transform_card. 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 transform_card? +

transform_card is provided by the Adaptive Cards MCP server (adaptive-cards-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Adaptive Cards

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.