Medium Risk

install_sdk

Get install commands and setup code for @kamydev/sdk in your framework.

Part of the Kamy server.

install_sdk can modify Kamy data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE KAMY →

Free to start. No card required.

AI agents use install_sdk to create or modify resources in Kamy. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call install_sdk repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Kamy.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "install_sdk": {
      "limits": [
        {
          "counter": "install_sdk_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Kamy policy for all 11 tools.

Get this rule live on your own Kamy server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY KAMY →

View all 11 tools →

These attack patterns abuse exactly the kind of access install_sdk gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so install_sdk only ever does what you allow.

SECURE KAMY →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the install_sdk tool do? +

Get install commands and setup code for @kamydev/sdk in your framework.. It is categorised as a Write tool in the Kamy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on install_sdk? +

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

What risk level is install_sdk? +

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

Can I rate-limit install_sdk? +

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

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

install_sdk is provided by the Kamy MCP server (https://mcp.kamy.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kamy tool call.

Deterministic rules across all 11 Kamy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.