sandbox_git_log

Commit history of a sandbox repo, paginated. Returns { items, nextCursor, hasMore } — pass nextCursor back as

SERVEREasyBits SOURCE@easybits.cloud/mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/sandbox-git-log.md

WHAT IT DOES

What sandbox_git_log does on EasyBits

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

RISK

Why sandbox_git_log is rated Medium

An AI agent can call sandbox_git_log faster than any human can review: one bad instruction and it creates or modifies resources in EasyBits by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sandbox_git_log safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sandbox_git_log, this is the rule to start with:

sandbox_git_log Rate-limited

sandbox_git_log 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": {
    "sandbox_git_log": {
      "limits": [
        {
          "counter": "sandbox_git_log_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every sandbox_git_log call is checked against it from then on.

FAQ

Questions about sandbox_git_log

What does the sandbox_git_log tool do? +

Commit history of a sandbox repo, paginated. Returns { items, nextCursor, hasMore } — pass nextCursor back as. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sandbox_git_log? +

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

What risk level is sandbox_git_log? +

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

Can I rate-limit sandbox_git_log? +

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

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

sandbox_git_log is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →