get_signing_key_ssh

Get the instance

SERVERForgejo SOURCEsqcows/forgejo-mcp

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/sqcows-forgejo-mcp/get-signing-key-ssh.md

WHAT IT DOES

What get_signing_key_ssh does on Forgejo

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

RISK

Why get_signing_key_ssh is rated Low

Retrieves SSH signing key data without modification or execution capability.

From the tool's definition Get the instance signing key SSH

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_signing_key_ssh safely

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

get_signing_key_ssh Allowed

get_signing_key_ssh 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": {
    "get_signing_key_ssh": {}
  }
}

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

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

FAQ

Questions about get_signing_key_ssh

What does the get_signing_key_ssh tool do? +

Get the instance. It is categorised as a Read tool in the Forgejo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_signing_key_ssh? +

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

What risk level is get_signing_key_ssh? +

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

Can I rate-limit get_signing_key_ssh? +

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

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

get_signing_key_ssh is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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