pinList · Xdevplatform/x MCP: Risk & Policy

WHAT IT DOES

What pinList does on Xdevplatform/xmcp

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

WHY IT NEEDS A POLICY

Why pinList needs a policy

This tool modifies user profile settings by pinning a list, which is a reversible write operation. It changes data (user preferences) but does not delete, execute code, move money, or perform irreversible actions. The scope is limited to the authenticated user's profile settings, resulting in low severity.

From the tool's definition Tool description states 'Pin a list for quick access in the authenticated user profile.' The verb 'pin' indicates a modification operation that creates or updates a user preference setting.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pinList Rate-limited

pinList 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": {
    "pinList": {
      "limits": [
        {
          "counter": "pinlist_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 Xdevplatform/xmcp, so you can run agents against it safely.

FAQ

Questions about pinList

What does the pinList tool do? +

Pin a list for quick access in the authenticated user profile. It is categorised as a Write tool in the Xdevplatform/xmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pinList? +

Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for pinList: 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 Xdevplatform/xmcp. Nothing to install.

What risk level is pinList? +

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

Can I rate-limit pinList? +

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

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

pinList is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

pinList is one line of Xdevplatform/x's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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