Find an object by a specific field value (safer than using IDs)
AI agents call find_object_by_field to retrieve information from pfSense Enhanced MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches or filters firewall configuration objects (rules, aliases, interfaces, etc.) by field criteria and returns matching results. It has no side effects—it does not create, modify, delete, or execute any actions. In the pfSense context, this is a supporting utility for locating configuration items, comparable to a database SELECT query.
From the tool's definition Tool name 'find_object_by_field' and description 'Find an object by a specific field value' indicate a query/lookup operation with no data modification.
Attacks that exploit this kind of access
Find an object by a specific field value (safer than using IDs). It is categorised as a Read tool in the pfSense Enhanced MCP Server MCP Server, which means it retrieves data without modifying state.
Register the pfSense Enhanced MCP Server MCP server in PolicyLayer and add a rule for find_object_by_field: 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 pfSense Enhanced MCP Server. Nothing to install.
find_object_by_field 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 find_object_by_field 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 find_object_by_field. 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.
find_object_by_field is provided by the pfSense Enhanced MCP Server MCP server (mmaxwellcb/pfsesen_mcp_2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →