AI agents call get_functions to retrieve information from Sdds without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a documentation/metadata retrieval tool with no capability to modify, delete, execute code, or affect financial systems. It simply fetches and returns information about available functions in the SDDS library. The read-only nature and informational purpose classify it as Read with low severity.
From the tool's definition Tool name 'get_functions' and description 'retrieves the combined description' indicate a read-only query operation. The tool accesses documentation/metadata about imported functions, HOCs, hooks, mixins, and utilities from a design system library.
Attacks that exploit this kind of access
This tool retrieves the combined description of imported ${libraryName} hocs, hooks, mixins, and utils from the functions section. It is categorised as a Read tool in the Sdds MCP Server, which means it retrieves data without modifying state.
Register the Sdds MCP server in PolicyLayer and add a rule for get_functions: 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 Sdds. Nothing to install.
get_functions 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_functions 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_functions. 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_functions is provided by the Sdds MCP server (@salutejs/sdds-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →