AI agents use manage_workspaces to create or update resources in MSFConsole MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MSFConsole MCP Server environment.
In Metasploit, workspaces are used to organize penetration testing data (hosts, services, vulnerabilities). 'Manage' implies create/update/delete operations. Without a description, the exact capabilities are unknown, but workspace management typically involves Write-level operations (creating, renaming, switching workspaces). It could also include deletion (Destructive), but without evidence I default to Write.
From the tool's definition Tool name 'manage_workspaces' on a Metasploit Framework MCP server; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access manage_workspaces gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MSFConsole MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_workspaces:
{
"version": "1",
"default": "deny",
"tools": {
"manage_workspaces": {
"limits": [
{
"counter": "manage_workspaces_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_workspaces stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
manage_workspaces. It is categorised as a Write tool in the MSFConsole MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MSFConsole MCP Server MCP server in PolicyLayer and add a rule for manage_workspaces: 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 MSFConsole MCP Server. Nothing to install.
manage_workspaces is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_workspaces 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 manage_workspaces. 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.
manage_workspaces is provided by the MSFConsole MCP Server MCP server (lyftium-inc/msfconsole-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MSFConsole MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 MSFConsole MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.