AI agents use teams_send_card to create or update resources in autoMate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your autoMate environment.
This tool creates new content (a card/message) in Microsoft Teams, which is a reversible Write action. It does not delete, execute arbitrary code, or move money. Severity is medium because unsolicited or malicious messages could disrupt team communication, but the blast radius is limited to message creation.
From the tool's definition Tool name 'teams_send_card' indicates sending a communication card to Microsoft Teams. The 'send' verb and context of a communication platform implies creating/posting a message or notification.
Documented attack patterns abuse exactly the kind of access teams_send_card gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for teams_send_card:
{
"version": "1",
"default": "deny",
"tools": {
"teams_send_card": {
"limits": [
{
"counter": "teams_send_card_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}teams_send_card stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
teams_send_card. It is categorised as a Write tool in the autoMate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the autoMate MCP server in PolicyLayer and add a rule for teams_send_card: 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 autoMate. Nothing to install.
teams_send_card 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 teams_send_card 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 teams_send_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.
teams_send_card is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.