Check SMB signing status to identify relay targets
AI agents call ad_smb_signing_check to retrieve information from pentestMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries SMB signing status on a target system to determine if it is vulnerable to relay attacks. It performs reconnaissance and returns status information without modifying, executing code, deleting data, or committing financial transactions. While the context (pentesting workflow, relay target identification) indicates offensive security use, the tool itself only reads/checks existing configuration state.
From the tool's definition Tool name: 'ad_smb_signing_check'. Description: 'Check SMB signing status to identify relay targets'. The verb 'check' and 'identify' indicate information retrieval about SMB signing configuration.
Documented attack patterns abuse exactly the kind of access ad_smb_signing_check gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and pentestMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ad_smb_signing_check:
{
"version": "1",
"default": "deny",
"tools": {
"ad_smb_signing_check": {}
}
}ad_smb_signing_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check SMB signing status to identify relay targets. It is categorised as a Read tool in the pentestMCP MCP Server, which means it retrieves data without modifying state.
Register the pentest MCP server in PolicyLayer and add a rule for ad_smb_signing_check: 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 pentestMCP. Nothing to install.
ad_smb_signing_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ad_smb_signing_check 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 ad_smb_signing_check. 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.
ad_smb_signing_check is provided by the pentest MCP server (ramkansal/pentestmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 pentestMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 pentestMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.