push_external_tool · Alaya MCP: Risk & Policy

WHAT IT DOES

What push_external_tool does on Alaya

AI agents use push_external_tool to create or update resources in Alaya — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Alaya environment.

WHY IT NEEDS A POLICY

Why push_external_tool needs a policy

This tool creates or modifies data reversibly by pushing a note to an external version control platform as an issue. While it involves external systems, it is fundamentally a Write operation (create issue). Severity is medium because misuse could spam external repositories or create unwanted issues, but the effects are reversible (issues can be closed/deleted).

From the tool's definition Tool description states 'Push a vault note to an external provider (gitlab, github) as an issue' — this creates new data (an issue) in an external system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

push_external_tool Rate-limited

push_external_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "push_external_tool": {
      "limits": [
        {
          "counter": "push_external_tool_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 Alaya, so you can run agents against it safely.

FAQ

Questions about push_external_tool

What does the push_external_tool tool do? +

Push a vault note to an external provider (gitlab, github) as an issue. It is categorised as a Write tool in the Alaya MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on push_external_tool? +

Register the Alaya MCP server in PolicyLayer and add a rule for push_external_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 Alaya. Nothing to install.

What risk level is push_external_tool? +

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

Can I rate-limit push_external_tool? +

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

How do I block push_external_tool completely? +

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

What MCP server provides push_external_tool? +

push_external_tool is provided by the Alaya MCP server (luke-kucing/alaya). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.