project_get_setting
Read a single ProjectSettings value by dotted key (e.g. application/config/name).
This record as markdown: /tools/breakpoint-mcp/project-get-setting.md
What project_get_setting does on Breakpoint
AI agents call project_get_setting to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | ProjectSettings key |
Parameters from the server's own tool schema.
Why project_get_setting is rated Low
This tool retrieves configuration settings by key lookup without modifying state, executing code, or causing destructive changes. It is a straightforward read operation with minimal risk of misuse.
From the tool's definition Tool description explicitly states "Read a single ProjectSettings value"; the verb "Read" and the retrieval-only operation (get by key) indicate no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs project_get_setting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For project_get_setting, this is the rule to start with:
project_get_setting is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every project_get_setting call is checked against it from then on.
Questions about project_get_setting
Read a single ProjectSettings value by dotted key (e.g. application/config/name). It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
project_get_setting accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for project_get_setting: 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 Breakpoint. Nothing to install.
project_get_setting 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 project_get_setting 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 project_get_setting. 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.
project_get_setting is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue