test_social_engineering
Run a social engineering assessment (phishing simulation, OSINT, DMARC audit). Returns immediately with engagement_id; agent runs asynchronously.
This record as markdown: /tools/0xsteph-pentest-ai/test-social-engineering.md
What test_social_engineering does on Pentest Ai
AI agents invoke test_social_engineering to trigger actions in Pentest Ai. 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.
Why test_social_engineering is rated High
This tool actively executes real-world offensive operations including phishing simulations and OSINT collection against external targets. These are active external operations with real side effects (sending phishing emails, probing targets), making Execute the appropriate category.
From the tool's definition 'Run a social engineering assessment (phishing simulation, OSINT, DMARC audit)' and 'agent runs asynchronously'
Attacks that exploit this kind of access
The rule that runs test_social_engineering safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pentest Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_social_engineering, this is the rule to start with:
test_social_engineering stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pentest Ai, apply this rule, and every test_social_engineering call is checked against it from then on.
Questions about test_social_engineering
Run a social engineering assessment (phishing simulation, OSINT, DMARC audit). Returns immediately with engagement_id; agent runs asynchronously. It is categorised as a Execute tool in the Pentest Ai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pentest Ai MCP server in PolicyLayer and add a rule for test_social_engineering: 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 Pentest Ai. Nothing to install.
test_social_engineering 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 test_social_engineering 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 test_social_engineering. 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.
test_social_engineering is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pentest Ai, and thousands of servers like it.
Across the catalogue