Skip to main content
Glama
eludden35

HIPAA Guardian MCP Server

getApiSecurityChecklist

Generate a comprehensive API security checklist to help healthcare application developers implement HIPAA-compliant security measures for protecting protected health information (PHI).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemaYes

Implementation Reference

  • The handler function that executes the tool logic, returning a static text response containing the OWASP-based API security checklist.
        async () => {
            return {
                content: [{
                    type: 'text',
                    text: `
    # General API Security Checklist (OWASP Based)
    
    1.  **Authentication:** Implement a standard, strong authentication mechanism (e.g., OAuth 2.0, JWT). Do not roll your own.
    2.  **Authorization:** Enforce authorization at every endpoint. Check that the authenticated user has the correct permissions to perform the requested action on the requested resource (e.g., User A cannot access User B's data).
    3.  **Input Validation:** Validate all incoming data for type, format, and length. Reject any invalid data. This protects against injection attacks.
    4.  **Rate Limiting:** Implement rate limiting to protect against denial-of-service (DoS) and brute-force attacks.
    5.  **Use HTTPS Everywhere:** All API endpoints must enforce TLS 1.2 or higher.
    6.  **Proper Error Handling:** Return generic error messages. Do not leak sensitive information like stack traces or internal function names.
    7.  **Security Headers:** Use security headers like Content-Security-Policy, Strict-Transport-Security, and X-Content-Type-Options.
    8.  **Logging and Monitoring:** Log all API requests and monitor for suspicious activity, such as high error rates or access attempts from unusual locations.
    `
                }]
            };
        }
  • The Zod schema for the tool input, defined as an empty object indicating no parameters are required.
    schema: z.object({}),
  • server.ts:298-323 (registration)
    The server.tool() call that registers the 'getApiSecurityChecklist' tool, including its description, schema, and inline handler function.
    server.tool(
        'getApiSecurityChecklist',
        {
            description: 'Provides a general-purpose checklist for securing backend APIs, based on OWASP best practices.',
            schema: z.object({}),
        },
        async () => {
            return {
                content: [{
                    type: 'text',
                    text: `
    # General API Security Checklist (OWASP Based)
    
    1.  **Authentication:** Implement a standard, strong authentication mechanism (e.g., OAuth 2.0, JWT). Do not roll your own.
    2.  **Authorization:** Enforce authorization at every endpoint. Check that the authenticated user has the correct permissions to perform the requested action on the requested resource (e.g., User A cannot access User B's data).
    3.  **Input Validation:** Validate all incoming data for type, format, and length. Reject any invalid data. This protects against injection attacks.
    4.  **Rate Limiting:** Implement rate limiting to protect against denial-of-service (DoS) and brute-force attacks.
    5.  **Use HTTPS Everywhere:** All API endpoints must enforce TLS 1.2 or higher.
    6.  **Proper Error Handling:** Return generic error messages. Do not leak sensitive information like stack traces or internal function names.
    7.  **Security Headers:** Use security headers like Content-Security-Policy, Strict-Transport-Security, and X-Content-Type-Options.
    8.  **Logging and Monitoring:** Log all API requests and monitor for suspicious activity, such as high error rates or access attempts from unusual locations.
    `
                }]
            };
        }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

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/eludden35/hipaa-guardian-mcp'

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