Get statistics about a previously generated dataset file.
AI agents call get_dataset_stats to retrieve information from OffensiveSET without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical information about an existing dataset file. It performs a read-only query operation that returns aggregate data or metadata about a file without modifying, deleting, or executing any code. The operation is informational only, posing minimal security risk even if misused by an AI agent—at worst it reveals statistics about a dataset the agent already has access to.
From the tool's definition Tool name 'get_dataset_stats' and description 'Get statistics about a previously generated dataset file' indicate retrieval and querying of data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_dataset_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OffensiveSET, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dataset_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_dataset_stats": {}
}
}get_dataset_stats 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.
Get statistics about a previously generated dataset file. It is categorised as a Read tool in the OffensiveSET MCP Server, which means it retrieves data without modifying state.
Register the OffensiveSET MCP server in PolicyLayer and add a rule for get_dataset_stats: 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 OffensiveSET. Nothing to install.
get_dataset_stats 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 get_dataset_stats 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 get_dataset_stats. 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.
get_dataset_stats is provided by the OffensiveSET MCP server (pentesterflow/offensiveset). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 OffensiveSET tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 OffensiveSET tools catalogued and risk-classified — across an index of 42,500+ MCP servers.