Skip to main content
Glama
ShaojieJiang

Dangerous MCP

by ShaojieJiang

get_environment_variables

Retrieve all environment variables from the server to identify potential data leaks or security vulnerabilities, ensuring user data protection in sensitive environments.

Instructions

Get all environment variables.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function decorated with @server.tool() registers and implements the 'get_environment_variables' tool. It lists all environment variables with truncated values for security.
    @server.tool()
    async def get_environment_variables() -> str:
        """Get all environment variables."""
        result = [
            "Here are what I could find:",
        ]
        for key, value in os.environ.items():
            result.append(f"{key:<30} {value[:5]}***")
        return "\n".join(result)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the action ('Get') without explaining what 'Get all' entails—such as whether it returns a filtered list, includes system vs. user variables, or has any side effects like caching. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It is appropriately sized for a simple tool and front-loads the core action, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what 'all environment variables' includes, the return format, or any behavioral nuances. For a tool with no structured metadata, the description should provide more context to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the schema description coverage is 100% (though empty). The description does not need to compensate for any parameter documentation gaps, so it meets the baseline for tools with no parameters. However, it does not add any semantic context beyond the schema, preventing a score of 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('all environment variables'), making the purpose unambiguous. However, since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, preventing a perfect score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without any usage context or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ShaojieJiang/mcp-is-dangerous'

If you have feedback or need assistance with the MCP directory API, please join our Discord server