Get available metafields for scan configuration.
AI agents call get_metafields to retrieve information from Threat Zone MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available metafields used in scan configuration. It is a read-only operation that queries system information and returns results. There are no side effects, data modifications, code execution, or destructive actions. The blast radius of misuse is minimal since it only exposes configuration schema information that would typically be available to authorized users of the service.
From the tool's definition Tool name 'get_metafields' and description 'Get available metafields for scan configuration' indicate a query/retrieval operation that returns configuration metadata without modifying any data.
Documented attack patterns abuse exactly the kind of access get_metafields gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Threat Zone MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_metafields:
{
"version": "1",
"default": "deny",
"tools": {
"get_metafields": {}
}
}get_metafields 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 available metafields for scan configuration. It is categorised as a Read tool in the Threat Zone MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Threat Zone MCP Server MCP server in PolicyLayer and add a rule for get_metafields: 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 Threat Zone MCP Server. Nothing to install.
get_metafields 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_metafields 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_metafields. 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_metafields is provided by the Threat Zone MCP Server MCP server (threat-zone/threatzonemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Threat Zone 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.
31 Threat Zone MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.