Refresh object IDs by re-querying an endpoint (handles ID changes after deletions)
AI agents call refresh_object_ids 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.
The tool's primary function is to fetch or synchronize object identifier data from the pfSense API endpoint. While it operates in a context where deletions may have occurred (causing ID changes), the tool itself only reads/queries to refresh its local state. No data is modified, deleted, or executed—only retrieved.
From the tool's definition Tool description states it 're-queries an endpoint' to refresh/retrieve object IDs. This is a query/retrieval operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Refresh object IDs by re-querying an endpoint (handles ID changes after deletions). 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 refresh_object_ids: 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.
refresh_object_ids 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 refresh_object_ids 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 refresh_object_ids. 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.
refresh_object_ids 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 →