Low Risk

get_employee

Get an employee by Id from QuickBooks Online.

How to control get_employee ↓

What get_employee does on QuickBooks Online MCP Server

AI agents call get_employee to retrieve information from QuickBooks Online MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_employee needs a policy

This tool retrieves employee information by ID. It is a pure read operation that queries existing data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal — exposure would be limited to unauthorized viewing of employee records. Low severity is appropriate for data retrieval operations.

From the tool's definition Tool name is 'get_employee' and description states 'Get an employee by Id from QuickBooks Online' — the verb 'get' indicates data retrieval with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_employee gives an agent:

How to control get_employee

PolicyLayer is an MCP gateway — it sits between your AI agents and QuickBooks Online MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_employee:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_employee": {}
  }
}

get_employee is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register QuickBooks Online MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_employee

What does the get_employee tool do? +

Get an employee by Id from QuickBooks Online. It is categorised as a Read tool in the QuickBooks Online MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_employee? +

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

What risk level is get_employee? +

get_employee is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_employee? +

Yes. Add a rate_limit block to the get_employee 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 get_employee completely? +

Set action: deny in the PolicyLayer policy for get_employee. 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 get_employee? +

get_employee is provided by the QuickBooks Online MCP Server MCP server (librechat-ai/quickbooks-online-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every QuickBooks Online MCP Server tool call.

Start from QuickBooks Online 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.

55 QuickBooks Online MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.