manage-enquiries · Fergus MCP Server MCP: Risk & Policy

WHAT IT DOES

What manage-enquiries does on Fergus MCP Server

AI agents use manage-enquiries to create or update resources in Fergus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fergus MCP Server environment.

WHY IT NEEDS A POLICY

Why manage-enquiries needs a policy

This tool performs reversible data creation (enquiries can be modified or deleted later). The 'create' action is the most severe capability and places it in the Write category. Severity is medium because misuse could generate spurious enquiries or spam the system, but the impact is limited to enquiry records and reversible. Confidence is high due to explicit description of capabilities.

From the tool's definition Tool description explicitly lists actions: 'get, list, create'. The 'create' action modifies data by adding new enquiries. 'Get' and 'list' are read operations, but the presence of 'create' elevates this to Write category since it can create new records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage-enquiries Rate-limited

manage-enquiries stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage-enquiries": {
      "limits": [
        {
          "counter": "manage-enquiries_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Fergus MCP Server, so you can run agents against it safely.

FAQ

Questions about manage-enquiries

What does the manage-enquiries tool do? +

Manage enquiries. Actions: get, list, create. It is categorised as a Write tool in the Fergus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage-enquiries? +

Register the Fergus MCP Server MCP server in PolicyLayer and add a rule for manage-enquiries: 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 Fergus MCP Server. Nothing to install.

What risk level is manage-enquiries? +

manage-enquiries is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage-enquiries? +

Yes. Add a rate_limit block to the manage-enquiries 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.

How do I block manage-enquiries completely? +

Set action: deny in the PolicyLayer policy for manage-enquiries. 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.

What MCP server provides manage-enquiries? +

manage-enquiries is provided by the Fergus MCP Server MCP server (jayco-design/fergus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.