Checks if the ${appName} IDE is installed on the user
AI agents call checkIdeInstalled to retrieve information from Tcsas Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries/retrieves information about whether an IDE is installed. It performs no write, execute, destructive, or financial operations. It is a simple read operation that returns a boolean or status result. The low severity reflects minimal blast radius—an AI agent misusing this tool cannot cause harm, as it merely checks a condition without side effects.
From the tool's definition Tool name 'checkIdeInstalled' and description 'Checks if the ${appName} IDE is installed on the user' indicate a query operation that retrieves installation status without modifying any system state.
Attacks that exploit this kind of access
Checks if the ${appName} IDE is installed on the user. It is categorised as a Read tool in the Tcsas Devtools MCP Server, which means it retrieves data without modifying state.
Register the Tcsas Devtools MCP server in PolicyLayer and add a rule for checkIdeInstalled: 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 Tcsas Devtools. Nothing to install.
checkIdeInstalled 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 checkIdeInstalled 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 checkIdeInstalled. 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.
checkIdeInstalled is provided by the Tcsas Devtools MCP server (tcmpp-team/tcsas-devtools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →