get_settings_info

THE RISK

Low Risk

Why get_settings_info needs a policy

This tool retrieves project settings information without creating, modifying, deleting, or executing anything. It is a simple query operation that returns existing configuration data. The minimal blast radius from misuse (an AI agent might read settings they shouldn't access, but cannot change system state) justifies low severity.

From the tool's definition Tool name 'get_settings_info' and description 'Get information about the project settings' clearly indicate data retrieval with no modification or execution. The verb 'get' and the informational nature (no side effects mentioned) confirm read-only behavior.

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

POLICY

How to control get_settings_info

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_settings_info": {}
  }
}

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

Create a free account and register Code Index — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Code Index tools

Destructive clear_settings Clear all settings and cached data. Execute build_deep_index Build the deep index (full symbol extraction) for the current project. This performs Execute refresh_index Manually rebuild the project file index. Use after git operations or when index seems stal Execute refresh_search_tools Manually re-detect the available command-line search tools on the system. This is usef Write configure_file_watcher configure_file_watcher Write create_temp_directory Create the temporary directory used for storing index data. Write set_project_path Set the base project path for indexing. Read check_temp_directory Check the temporary directory used for storing index data.

All 14 Code Index tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_settings_info

What does the get_settings_info tool do? +

Get information about the project settings. It is categorised as a Read tool in the Code Index MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_settings_info? +

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

What risk level is get_settings_info? +

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

Can I rate-limit get_settings_info? +

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

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

get_settings_info is provided by the Code Index MCP server (johnhuang316/code-index-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Code Index tool call.

Start from Code Index, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →