get_directory_indexing_status

Get directory indexing configuration for security

SERVER20i MCP Server SOURCEcbrown35/20i-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cbrown35-20i-mcp/get-directory-indexing-status.md

What get_directory_indexing_status does on 20i MCP Server

AI agents call get_directory_indexing_status to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_directory_indexing_status is rated Low

This tool performs information retrieval only. It fetches the current configuration state of directory indexing, which is a passive, non-mutating operation with no side effects. No data is created, modified, deleted, or executed. The blast radius if misused is minimal—an agent could at worst learn security configuration details, but cannot alter infrastructure or permissions.

From the tool's definition Tool name 'get_directory_indexing_status' and description 'Get directory indexing configuration for security' indicate a read-only retrieval operation that queries the current state of directory indexing settings without modifying or deleting any data.

Questions about get_directory_indexing_status

What does the get_directory_indexing_status tool do? +

Get directory indexing configuration for security. It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_directory_indexing_status? +

Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_directory_indexing_status: 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 20i MCP Server. Nothing to install.

What risk level is get_directory_indexing_status? +

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

Can I rate-limit get_directory_indexing_status? +

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

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

get_directory_indexing_status is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on 20i MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 20i MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.