active_scan
AI agents invoke active_scan to trigger actions in BasicSec MCP Server. 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.
The server description distinguishes between passive and active scanning. Active scanning typically involves sending probes or making connections to external systems (like SMTP connectivity tests), which constitutes executing external operations. However, the tool description is empty, so confidence is reduced.
From the tool's definition Tool name 'active_scan' on a server that provides 'active scanning capabilities' and 'SMTP connectivity testing'
Attacks that exploit this kind of access
active_scan. It is categorised as a Execute tool in the BasicSec MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the BasicSec MCP Server MCP server in PolicyLayer and add a rule for active_scan: 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 BasicSec MCP Server. Nothing to install.
active_scan 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 active_scan 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 active_scan. 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.
active_scan is provided by the BasicSec MCP Server MCP server (marlinkcyber/basicsec-mcp). 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 →