sec_check_https_usage

Verifica que el codigo use HTTPS en lugar de HTTP. Parametros: filename.

SERVERMCP Framework Personal SOURCEinggerman/mcps

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/inggerman-mcps/sec-check-https-usage.md

WHAT IT DOES

What sec_check_https_usage does on MCP Framework Personal

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

RISK

Why sec_check_https_usage is rated Low

Even though sec_check_https_usage only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sec_check_https_usage safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sec_check_https_usage, this is the rule to start with:

sec_check_https_usage Allowed

sec_check_https_usage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sec_check_https_usage": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every sec_check_https_usage call is checked against it from then on.

FAQ

Questions about sec_check_https_usage

What does the sec_check_https_usage tool do? +

Verifica que el codigo use HTTPS en lugar de HTTP. Parametros: filename. It is categorised as a Read tool in the MCP Framework Personal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sec_check_https_usage? +

Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for sec_check_https_usage: 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 MCP Framework Personal. Nothing to install.

What risk level is sec_check_https_usage? +

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

Can I rate-limit sec_check_https_usage? +

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

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

sec_check_https_usage is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Framework Personal, and thousands of servers like it.

This server

All 643 MCP Framework Personal tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →