Get the props/API of a specific component
AI agents call get_component_props 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 and queries component property information from the design system. It performs a read-only operation with no side effects—it does not create, modify, delete, or execute anything. The retrieved data helps AI agents understand component APIs to avoid duplication, which is the stated purpose of the MCP server.
From the tool's definition Tool name 'get_component_props' and description 'Get the props/API of a specific component' indicate retrieval of component metadata without modification or execution.
Documented attack patterns abuse exactly the kind of access get_component_props 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_component_props:
{
"version": "1",
"default": "deny",
"tools": {
"get_component_props": {}
}
}get_component_props 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 the props/API of a specific component. 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_component_props: 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_component_props 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_component_props 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_component_props. 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_component_props 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.