pfsense_create_graphql
A execute tool on the Pfsense MCP server.
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-create-graphql.md
What pfsense_create_graphql does on Pfsense
AI agents invoke pfsense_create_graphql to trigger actions in Pfsense. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why pfsense_create_graphql is rated High
The tool name 'pfsense_create_graphql' suggests interaction with a GraphQL endpoint. GraphQL can perform both reads and writes (mutations), and on a firewall management platform, even read operations can expose sensitive configuration data. The 'create' prefix suggests it may be creating a GraphQL query or executing a mutation.
From the tool's definition Tool name contains 'graphql' suggesting it creates or executes a GraphQL query/mutation against the pfSense REST API; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs pfsense_create_graphql safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pfsense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pfsense_create_graphql, this is the rule to start with:
pfsense_create_graphql stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pfsense, apply this rule, and every pfsense_create_graphql call is checked against it from then on.
Questions about pfsense_create_graphql
pfsense_create_graphql is a execute tool on the Pfsense MCP server. It is categorised as a Execute tool in the Pfsense MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_create_graphql: 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. Nothing to install.
pfsense_create_graphql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pfsense_create_graphql 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 pfsense_create_graphql. 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.
pfsense_create_graphql is provided by the Pfsense MCP server (abl030/pfsense-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pfsense, and thousands of servers like it.
Across the catalogue