This record as markdown: /tools/yuga-hashimoto-localant/skill-disable.md
What skill_disable does on LocalAnt
AI agents use skill_disable to create or update resources in LocalAnt, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LocalAnt environment.
Why skill_disable is rated Medium
Disabling a skill modifies system configuration by turning off a capability, but this is likely reversible (the skill can be re-enabled). This falls under Write rather than Destructive. The blast radius is medium since disabling a skill could remove important functionality from the gateway, potentially disrupting automated workflows.
From the tool's definition 'Disable a skill' — reversibly disables a skill (can presumably be re-enabled)
Attacks that exploit this kind of access
The rule that runs skill_disable safely
PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For skill_disable, this is the rule to start with:
skill_disable 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 LocalAnt, apply this rule, and every skill_disable call is checked against it from then on.
Questions about skill_disable
Disable a skill. It is categorised as a Write tool in the LocalAnt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LocalAnt MCP server in PolicyLayer and add a rule for skill_disable: 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 LocalAnt. Nothing to install.
skill_disable 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 skill_disable 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 skill_disable. 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.
skill_disable is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on LocalAnt, and thousands of servers like it.
This server
Across the catalogue