Get a specific design token by its full name
AI agents call get_token to retrieve information from Ds Pilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves design token metadata (likely values like colors, spacing, typography) by name. It performs a read-only query operation with no capability to modify, execute code, delete data, or trigger external actions. The blast radius of misuse is minimal—an AI agent could only access existing token values within the design system. This is categorized as Read per the taxonomy.
From the tool's definition Tool name 'get_token' and description 'Get a specific design token by its full name' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_token gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ds Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for get_token:
{
"version": "1",
"default": "deny",
"tools": {
"get_token": {}
}
}get_token is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a specific design token by its full name. It is categorised as a Read tool in the Ds Pilot MCP Server, which means it retrieves data without modifying state.
Register the Ds Pilot MCP server in PolicyLayer and add a rule for get_token: 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 Ds Pilot. Nothing to install.
get_token is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_token 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.
Set action: deny in the PolicyLayer policy for get_token. 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.
get_token is provided by the Ds Pilot MCP server (lyse-labs/ds-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ds Pilot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Ds Pilot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.