revoke_agent_tool
Remove ONE specific tool from an agent's loadout (tool_access). Use when an operator says "take <tool> away from <agent>" — or to clean a phantom/stale name out of a loadout (unresolvable names ARE removable here, unlike grant). Reports honestly when the name was not present, and when the tool is...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/revoke-agent-tool.md
What revoke_agent_tool does on Freedom Mcp
AI agents use revoke_agent_tool to create or update resources in Freedom Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freedom Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | Yes | UUID of the agent. Use get_team_roster to find IDs. |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
tool_name | string | Yes | Exact loadout entry to remove (phantom/stale names allowed). |
Parameters from the server's own tool schema.
Why revoke_agent_tool is rated Medium
Modifies agent configuration by revoking tool access; reversible by re-granting the tool.
From the tool's definition Remove ONE specific tool from an agent's loadout (tool_access)
Attacks that exploit this kind of access
The rule that runs revoke_agent_tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revoke_agent_tool, this is the rule to start with:
revoke_agent_tool 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every revoke_agent_tool call is checked against it from then on.
Questions about revoke_agent_tool
Remove ONE specific tool from an agent's loadout (tool_access). Use when an operator says "take <tool> away from <agent>" — or to clean a phantom/stale name out of a loadout (unresolvable names ARE removable here, unlike grant). Reports honestly when the name was not present, and when the tool is a universal base tool the runtime keeps available regardless. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Write tool in the Freedom Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
revoke_agent_tool accepts 3 parameters: agent_id, companyId, tool_name. Required: agent_id, companyId, tool_name. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for revoke_agent_tool: 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 Freedom Mcp. Nothing to install.
revoke_agent_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the revoke_agent_tool 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 revoke_agent_tool. 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.
revoke_agent_tool is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue