Telegram MCP Enhanced

Overview Schema Source Related Servers Discussions Admin

security_status

Reports enforced security and reliability policy—permitted operations, access controls, rate limits, prompt-injection mode, and scheduler state—so you can check allowed actions and explain refusals.

Instructions

Report the security and reliability policy this server enforces.

Added by Telegram MCP Enhanced. Use it when you need to know what you are
allowed to do before attempting an operation, or to explain to the user why
a request was refused. It reports policy only: no credentials, no session
data, no chat identifiers and no message content are ever included.

Returns:
    `SecurityStatus`: Which operations are permitted, whether chat access
        control and rate limiting are active, the prompt-injection mode in
        force, and current scheduler state.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`dry_run`	No
`scheduler`	Yes
`rate_limit`	Yes
`chat_access`	Yes
`permissions`	Yes
`permission_profiles`	No
`confirmation_required`	No
`prompt_injection_detection`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does well by stating that it reports policy only and never includes credentials, session data, chat identifiers, or message content. It also summarizes the returned policy dimensions, though it stops short of explicitly saying 'read-only' or 'no side effects' in annotation-style terms.

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

Conciseness4/5

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

The description is front-loaded and generally efficient, leading with the purpose and then usage guidance. The 'Added by Telegram MCP Enhanced' note and the return-value summary are slightly extraneous given the output schema, but they do not materially distract.

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

Completeness5/5

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

For a zero-parameter status tool with an output schema, the description supplies enough context: what it reports, when to use it, and what sensitive data it excludes. Nothing needed to invoke or interpret the tool correctly is missing.

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 takes zero parameters, so the baseline is 4. The description correctly does not invent parameter semantics and keeps the focus on the policy report itself.

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

Purpose5/5

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

The description uses a specific verb ('Report') and resource ('security and reliability policy this server enforces'), making the tool's purpose unambiguous. It is clearly distinguishable from the sibling message-operation tools because it is a policy/status endpoint rather than a chat action.

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

Usage Guidelines5/5

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

It explicitly says when to use it: before attempting an operation to learn what is allowed, or to explain to the user why a request was refused. No sibling tool performs the same role, so there is no meaningful alternative to route to.

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

Deploy Server