New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

run_fatcat

A execute tool on the Pentester- MCP server.

SERVERPentester-MCP SOURCEhalilkirazkaya/pentester-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/halilkirazkaya-pentester-mcp/run-fatcat.md

What run_fatcat does on Pentester-MCP

AI agents invoke run_fatcat to trigger actions in Pentester-MCP. 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 run_fatcat is rated High

This tool executes an external penetration testing utility (fatcat), which performs reconnaissance and potentially exploitative operations against databases. Execution tools have high severity because their effects depend entirely on user-supplied arguments and attacker intent. While not immediately destructive like DELETE commands, unauthorized execution could enable reconnaissance leading to compromise.

From the tool's definition Tool named 'run_fatcat' on Pentester-MCP server which 'Enables AI assistants to autonomously execute over 200 open-source penetration testing tools'. The 'run_' prefix indicates execution of an external tool.

Questions about run_fatcat

What does the run_fatcat tool do? +

run_fatcat is a execute tool on the Pentester MCP server. It is categorised as a Execute tool in the Pentester-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_fatcat? +

Register the Pentester MCP server in PolicyLayer and add a rule for run_fatcat: 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 Pentester-MCP. Nothing to install.

What risk level is run_fatcat? +

run_fatcat is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_fatcat? +

Yes. Add a rate_limit block to the run_fatcat 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.

How do I block run_fatcat completely? +

Set action: deny in the PolicyLayer policy for run_fatcat. 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.

What MCP server provides run_fatcat? +

run_fatcat is provided by the Pentester MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Pentester, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Pentester's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.