Low Risk

get_source_code

Fetch component source code bundle from https://ui-layouts.com/r/{key}.json (or custom filename), list files and optionally return a specific file content.

How to control get_source_code ↓

What get_source_code does on Ui Layouts

AI agents call get_source_code to retrieve information from Ui Layouts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_source_code needs a policy

This tool performs read-only operations: fetching source code bundles and listing/retrieving file contents from ui-layouts.com. There are no side effects, data modifications, code execution, or destructive operations. The severity is low because exposing public source code via a read-only interface poses minimal risk—an AI agent cannot cause harm by retrieving already-public component code.

From the tool's definition The tool 'fetch[es] component source code' and 'list[s] files and optionally return[s] a specific file content' from a public CDN endpoint. It retrieves data with no ability to modify, delete, or execute code.

Documented attack patterns abuse exactly the kind of access get_source_code gives an agent:

How to control get_source_code

PolicyLayer is an MCP gateway — it sits between your AI agents and Ui Layouts, and nothing reaches the server without passing your rules. This is the rule we recommend for get_source_code:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_source_code": {}
  }
}

get_source_code is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Ui Layouts — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_source_code

What does the get_source_code tool do? +

Fetch component source code bundle from https://ui-layouts.com/r/{key}.json (or custom filename), list files and optionally return a specific file content. It is categorised as a Read tool in the Ui Layouts MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_source_code? +

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

What risk level is get_source_code? +

get_source_code is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_source_code? +

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

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

get_source_code is provided by the Ui Layouts MCP server (ui-layouts/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ui Layouts tool call.

Start from Ui Layouts, 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 Ui Layouts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.