This record as markdown: /tools/adbutler/get-manager.md
What get_manager does on AdButler
AI agents call get_manager to retrieve information from AdButler without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Manager ID |
Parameters from the server's own tool schema.
Why get_manager is rated Low
This tool retrieves information about a manager entity by ID. It queries and returns data without side effects, aligning with the Read category. The severity is low because retrieving manager details poses minimal risk; there is no capability to modify, delete, or trigger external operations. The high confidence reflects the clear, unambiguous nature of a simple getter function.
From the tool's definition Tool name 'get_manager' with description 'Get details of a specific manager by ID' — a straightforward retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_manager safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_manager, this is the rule to start with:
get_manager is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every get_manager call is checked against it from then on.
Questions about get_manager
Get details of a specific manager by ID. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_manager accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for get_manager: 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 AdButler. Nothing to install.
get_manager 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 get_manager 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 get_manager. 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.
get_manager is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue