sandbox_credentials_grant

Run sandbox-credentials.grant through the Appaloft application operation catalog. Shared with HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp
High RISK CLASS
Category Execute
Parameters 65 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/sandbox-credentials-grant.md

What sandbox_credentials_grant does on Appaloft

AI agents invoke sandbox_credentials_grant to trigger actions in Appaloft. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

ParameterTypeRequiredDescription
grantId string Yes
sandboxId string Yes
secretRef string Yes
destination string Yes
parameterName string
transformation string Yes

Parameters from the server's own tool schema.

Why sandbox_credentials_grant is rated High

sandbox_credentials_grant triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts file system path (destination)

Questions about sandbox_credentials_grant

What does the sandbox_credentials_grant tool do? +

Run sandbox-credentials.grant through the Appaloft application operation catalog. Shared with HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does sandbox_credentials_grant accept? +

sandbox_credentials_grant accepts 6 parameters: grantId, sandboxId, secretRef, destination, parameterName, transformation. Required: grantId, sandboxId, secretRef, destination, transformation. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sandbox_credentials_grant? +

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

What risk level is sandbox_credentials_grant? +

sandbox_credentials_grant is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sandbox_credentials_grant? +

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

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

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

More on Appaloft, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appaloft's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.