# get_stackcache_settings

Get StackCache performance settings

Agent View of the PolicyLayer registry record for `get_stackcache_settings`. HTML page: https://policylayer.com/tools/cbrown35-20i-mcp/get-stackcache-settings

## Facts

- Tool: `get_stackcache_settings`
- Server: 20i MCP Server (`cbrown35/20i-mcp`) — https://policylayer.com/tools/cbrown35-20i-mcp.md
- Homepage: https://github.com/Cbrown35/20i-MCP
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_stackcache_settings",
    "arguments": {}
  }
}
```

## Why get_stackcache_settings is rated Low

This tool retrieves configuration or performance metrics for StackCache (a caching service), similar to a 'get' or 'fetch' operation. It reads existing settings without creating, modifying, deleting, or executing any operations. The blast radius is minimal—at worst, exposed cache configuration details could inform optimization efforts, but no systems are altered by calling this tool.

From the tool's own definition: "Tool name 'get_stackcache_settings' and description 'Get StackCache performance settings' indicate data retrieval with no modification or side effects."

## Use case

AI agents call get_stackcache_settings 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 20i MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_stackcache_settings": {}
  }
}
```

## Other tools on 20i MCP Server (301)

- `deactivate_package` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/deactivate-package.md
- `deactivate_vps` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/deactivate-vps.md
- `delete_application` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/delete-application.md
- `delete_cdn_security_headers` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/delete-cdn-security-headers.md
- `delete_easy_builder_instance` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/delete-easy-builder-instance.md
- `delete_hosting_package` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/delete-hosting-package.md
- `delete_mssql_database` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/delete-mssql-database.md
- `delete_package` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/delete-package.md
- `manage_directories` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/manage-directories.md
- `manage_wordpress_plugin` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/manage-wordpress-plugin.md
- `purge_cdn_cache` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/purge-cdn-cache.md
- `rebuild_vps` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/rebuild-vps.md
- `reinstall_software` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/reinstall-software.md
- `reinstall_wordpress` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/reinstall-wordpress.md
- `remove_country_block` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/remove-country-block.md
- `remove_ip_block` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/remove-ip-block.md
- `remove_mssql_user` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/remove-mssql-user.md
- `remove_ssl_certificates` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/remove-ssl-certificates.md
- `remove_stack_user_from_package` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/remove-stack-user-from-package.md
- `remove_subdomain` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/remove-subdomain.md
- `reset_managed_vps_profile` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/reset-managed-vps-profile.md
- `restore_ftp_backup` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/restore-ftp-backup.md
- `restore_snapshot` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/restore-snapshot.md
- `shutdown_vps` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/shutdown-vps.md
- `suspend_package` — Destructive — https://policylayer.com/tools/cbrown35-20i-mcp/suspend-package.md
- `activate_vps` — Execute — https://policylayer.com/tools/cbrown35-20i-mcp/activate-vps.md
- `change_vps_root_password` — Execute — https://policylayer.com/tools/cbrown35-20i-mcp/change-vps-root-password.md
- `clone_wordpress_staging` — Execute — https://policylayer.com/tools/cbrown35-20i-mcp/clone-wordpress-staging.md
- `deploy_application` — Execute — https://policylayer.com/tools/cbrown35-20i-mcp/deploy-application.md
- `deploy_website_complete` — Execute — https://policylayer.com/tools/cbrown35-20i-mcp/deploy-website-complete.md
- …and 271 more: https://policylayer.com/tools/cbrown35-20i-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=cbrown35-20i-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/cbrown35-20i-mcp