Test SMTP configuration (admin only)
AI agents invoke planka_test_smtp to trigger actions in Planka MCP Server for Claude. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Testing SMTP configuration initiates an external network operation (connecting to an SMTP server, potentially sending a test email). This is an Execute-category action as it triggers an external operation. It is admin-only, raising the severity, but the blast radius is limited since it's primarily a connectivity test rather than a destructive or financial action.
From the tool's definition 'Test SMTP configuration' — triggers an external SMTP connection/email test operation
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Test SMTP configuration (admin only). It is categorised as a Execute tool in the Planka MCP Server for Claude MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Planka MCP Server for Claude MCP server in PolicyLayer and add a rule for planka_test_smtp: 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 Planka MCP Server for Claude. Nothing to install.
planka_test_smtp 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 planka_test_smtp 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 planka_test_smtp. 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.
planka_test_smtp is provided by the Planka MCP Server for Claude MCP server (nextheberg/planka-mcp-server-for-claude). 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 →